To illustrate some of the points that came up in this discussion, I have
added several examples to the scrollbar-gutter explainer:
https://github.com/felipeerias/scrollbar-gutter-explainer#examples
These should run well in Chrome after enabling the "Experimental Web
Platform features" in
Hello WebKit,
Due to planned infrastructure maintenance, our critical continuous
integration services (EWS and post-commit bots) will be unavailable
during the following weekends:
*Dates*:
*Begin*: Friday, March 5th, 2021. 5pm (PST)
*End*: Monday, March 8th, 2021. No later than 6pm (PST)
Thank you very much.
In terms of the clarity of the API, I am not sure that it would be a
good idea to split the existing functionality into one property and
several environment variables.
One drawback of env variables is that there will probably be quite a few
of them to take into account,
Thank you very much.
I understand that your concern is mainly about the "always" keyword of
scrollbar-gutter, where space is reserved for the scrollbar regardless
of whether it is of the fixed or overlay kind.
This keyword is intended as a simple solution for situations where the
overlay
4 matches
Mail list logo
