Why would it be out of scope for CSS? CSS explicitly mentions scrollbars (overflow:scroll, for one). Why shouldn't its spec explicitly include the expected location of those scrollbars? Aharon On Thu, Oct 7, 2010 at 11:26 AM, fantasai <fantasai.lists@inkedblade.net>wrote: > On 10/06/2010 09:10 AM, Aharon (Vladimir) Lanin wrote: > >> Amit Aronovitch wrote: >> >>> I see that the editor is rejecting the proposals regarding UI issues >>> (keyboard >>> shortcut for direction-switching, location of the scrollbar, etc.). >>> While this seems justified (after all, this is really out of scope for >>> the >>> HTML spec), I feel that these proposals should not be lost, and should be >>> >> > kept in a way that is likely to reach browser-developers >> >>> Perhaps an "implementation guidelines" page, or appendix, on the W3C >>> site. >>> >> >> I agree. The proposal itself is a (draft, for now) W3C Note, and that >> should count for something, but we should figure out in what other W3C >> documents such requirements should be mentioned. >> >> Regarding the scrollbars, I intend to get the requirement into the CSS >> spec. >> > > I believe it is also out-of-scope for CSS. I think you need a > W3C i18nWG Best Practices for Browser UI and BIDI Note or > somesuch. > > CCing Tantek, though, since he's in charge of CSS3 UI. > > Tantek, the issue is that the i18n-bidi subgroup wants to recommend that > scrollbar location always matches the OS defaults and does not change > with the contents of the page, even if those contents are affected by > bidi. > > ~fantasai >
Received on Thursday, 7 October 2010 12:11:43 UTC