The `gazetasp.com.br` site in bug 1925937 uses styles like the third part of my testcase (*both* width:0 and height:0). If we suspect other sites might be doing the same thing with a similar scrollbar-hiding intent, we might consider special-casing `::-webkit-scrollbar { width: 0; height: 0; }` as behaving like `scrollbar-width: none`. (where "0" could also be e.g. "0px", etc) (We might also try to get the single-axis-collapsing, but as of now we don't have any confirmation that sites actually do that, so maybe that's something to not worry about until we have a demonstration that it's needed.) hiro, what do you think? Do you have cycles to craft a followup along those lines? (As of now I only know of one WebCompat Site Report that would benefit from this, so maybe not a high reward, but also perhaps pretty low-cost as well, since I imagine a lot of the supporting pieces are now already there.)
Bug 2028308 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The `gazetasp.com.br` site in bug 1925937 uses styles like the third part of my testcase (specifying *both* width:0 and height:0). If we suspect other sites might be doing the same thing with a similar scrollbar-hiding intent, we might consider special-casing `::-webkit-scrollbar { width: 0; height: 0; }` as behaving like `scrollbar-width: none`. (where "0" could also be e.g. "0px", etc) (We might also try to get the single-axis-collapsing, but as of now we don't have any confirmation that sites actually do that, so maybe that's something to not worry about until we have a demonstration that it's needed.) hiro, what do you think? Do you have cycles to craft a followup along those lines? (As of now I only know of one WebCompat Site Report that would benefit from this, so maybe not a high reward, but also perhaps pretty low-cost as well, since I imagine a lot of the supporting pieces are now already there.)
The `gazetasp.com.br` site in bug 1925937 uses styles like the third part of my testcase (specifying *both* width:0 and height:0). If we suspect other sites might be doing the same thing with a similar scrollbar-hiding intent, we might consider special-casing `::-webkit-scrollbar { width: 0; height: 0; }` as behaving like `scrollbar-width: none`. (Where sites might use e.g. "0px" etc instead of literal `0`.) (We might also try to get the single-axis-collapsing, but as of now we don't have any confirmation that sites actually do that, so maybe that's something to not worry about until we have a demonstration that it's needed.) hiro, what do you think? Do you have cycles to craft a followup along those lines? (As of now I only know of one WebCompat Site Report that would benefit from this, so maybe not a high reward, but also perhaps pretty low-cost as well, since I imagine a lot of the supporting pieces are now already there.)
The `gazetasp.com.br` site in bug 1925937 uses styles like the third part of my testcase (specifying *both* width:0 and height:0). If we suspect other sites might be doing the same thing with a similar scrollbar-hiding intent, we might consider special-casing `::-webkit-scrollbar { width: 0; height: 0; }` as behaving like `scrollbar-width: none`. (Where sites might use e.g. "0px" etc instead of literal `0`.) (We might also try to get the single-axis-collapsing from the first and second part of my testcase -- but as of now, we don't have any confirmation that sites actually do that, so maybe that's something to not worry about until we have a demonstration that it's needed.) hiro, what do you think? Do you have cycles to craft a followup along those lines? (As of now I only know of one WebCompat Site Report that would benefit from this, so maybe not a high reward, but also perhaps pretty low-cost as well, since I imagine a lot of the supporting pieces are now already there.)