Can't get the youtube player seekbar to remain unaffected, while the rest of the page recolored, works with old CTS css which can't be imported.

14 views
Skip to first unread message

dqe...@gmail.com

unread,
Feb 22, 2016, 4:34:49 AM2/22/16
to Color That Site!
Hi!

I have this complicated issue.
With my old css the new comment textbox remains white. So I decided to update it with re-init (and starting from scratch too). However the seekbar's color also changed now which was formerly set ad don't change.
After setting it's color to don't change, much of the page also became white. And I can't have it changed because it looses its transparency and I don't see where the buffering state.

From my backup account I tried exporting the old css, but it didn't work. When imported the seekbak was also effected now.

Can I resolve this issue somehow? Can I manually edit the css and manually edit the part for that element?

I guess the issue is that they changed the seekbar color to something that matches a page background color. So I can't do that with the features this addon provides.

I attached some pictures

cts-old.png
cts-new.png
cts-copy.png

dqe...@gmail.com

unread,
Feb 22, 2016, 5:01:50 AM2/22/16
to Color That Site!, dqe...@gmail.com
Okay. So it seems I succeded.
Though I could only find the the CSS file based on creation/modification date since it had uninformative name and no metadata.

And I have to be careful not to change anything in it's entry. Not even it's name, otherwise it gets overwritten...

Michael

unread,
Feb 22, 2016, 5:36:06 AM2/22/16
to Color That Site!, dqe...@gmail.com
Hi,
I'm happy that it works. Honestly, I don't have that bar in my Youtube. Are you still using Flash? (Mine uses the HTML5 player).

I tried the Addon on Youtube (HTML5) and it worked. However what you said still could happen (also without Flash).

CTS color edits consist of "rule set" based on background and foreground colors. Even images are converted internally to some simplified color based rule. CTS then uses a page and creates a User CSS based on these rules. If you "Reinitialize" a Color Edit or import one, this CSS is newly created.

One reason for this is to make the edit more independent from a specific CSS.
One disadvantage is, that you can only define one equivalent color for a specific background and/or foreground color.

The export/import function also uses these rules. One other reason is that the User CSS can contain changed images of the site. Exporting & passing these along could cause copyright problems.


As you've already found out, you can edit the User CSS. They're saved in the "ColourThatSite\css" subfolder of the Firefox Profile folder.
...and they will be overwritten, each time when you change & save that color edit.

Another possibility is to create a custom rule in the Add-on Stylish or use the entire UserCSS there.

dqe...@gmail.com

unread,
Feb 22, 2016, 6:09:54 AM2/22/16
to Color That Site!, dqe...@gmail.com
That bar is added by an addon. It's not relevant though.

I'm also using the HTML5 player, hence the issue with the seekbar. (CSS can't effect flash as far as I know)


...and they will be overwritten, each time when you change & save that color edit.

The stuff in the sqlite database can't be edited? I assume the CSS file is generated from that, because it's not only rewritten when I change colors, but also when I change the item's name.

By the way. This would be a lot less of an issue if transparency wasn't lost on the seekbar. But since it does it's impossible to tell how much is buffered and doesn't show where I hover the mouse. It also looks rather unappealing without transparency, it stick out from the video.

dqe...@gmail.com

unread,
Mar 1, 2016, 5:49:12 AM3/1/16
to Color That Site!, dqe...@gmail.com
CTS color edits consist of "rule set" based on background and foreground colors. Even images are converted internally to some simplified color based rule. CTS then uses a page and creates a User CSS based on these rules. If you "Reinitialize" a Color Edit or import one, this CSS is newly created.

One reason for this is to make the edit more independent from a specific CSS.
One disadvantage is, that you can only define one equivalent color for a specific background and/or foreground color.


BTW I understand this, but still thing that ignoring/removing transparency (which is the other major part of this issue) is a bug/flaw. In this case it broke part of the seekbars functionality. (Invisible buffer, and no hover feedback)
Since this addon does not allow to change transparency it should leave transparency as it was and only change the color.
I also had stuff appearing before that shouldn't be there. Now I guess it's because of this problem.
For example this on mozillazine after setting bitmaps to "recalculate all":



Reply all
Reply to author
Forward
0 new messages