46 bytes, text/x-phabricator-request
|Details | Review|
No description provided.
Is that for Nightly or do you mean to let them ride the trains to release? Sebastian
I'm thinking about having it ride the train, but I'd wait for CSSWG to publish it first.
Comment on attachment 9012023 [details] Bug 1492012 - Enable scrollbar-color and scrollbar-width by default. r=heycam Cameron McCormack (:heycam) has approved the revision.
Attachment #9012023 - Flags: review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/9ed4cd3adbbb Enable scrollbar-color and scrollbar-width by default. r=heycam
Sorry, does this mean Nightly users will be able to change scrollbar's colors and width?
CSS properties are mainly for websites to customize their user experience, but yes, users can always use those properties in their user stylesheets to customize their own experience as well.
(In reply to Xidorn Quan [:xidorn] UTC+10 from comment #8) > CSS properties are mainly for websites to customize their user experience, > but yes, users can always use those properties in their user stylesheets to > customize their own experience as well. Sure, thank you so much for answering me so quickly!
Love this feature! Firefox Nightly seems to only support keywords. Will you also support length as a value?
(In reply to oliverwilliams345 from comment #10) > Love this feature! Firefox Nightly seems to only support keywords. Will you > also support length as a value? That was the initial approach, but other CSSWG members opposed, so the resolution ended up being allowing only keywords.
No, it's not very likely that scrollbar-width will support accepting length, and that will probably be removed from the spec soon. Operating system vendors expressed strongly against doing that.
Thanks for clarifying! `thin` looks nice and I don't think there's a pressing need for a specified width. Looks like rgba values ignore the alpha value in Firefox Nightly. Is that intentional?
I'm fixing that in bug 1494607 (and another bug for macOS to come). Ignoring that was easier to implement and I didn't think that matters a lot, but it seems people do have some expectation for that, so I'm trying to fix it now.
Thanks Xidorn :)
Rachel Andrew already documented this spec. I've finished it off by making sure compat data is up-to-date for both: https://github.com/mdn/browser-compat-data/pull/3063 And adding a note to the Fx64 rel notes: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/64#CSS
You need to log in before you can comment on or make changes to this bug.