- From: Ehsan Akhgari <ehsan@mozilla.com>
- Date: Thu, 25 Nov 2010 18:13:29 -0500
- To: "Aharon (Vladimir) Lanin" <aharon@google.com>
- Cc: CE Whitehead <cewcathar@hotmail.com>, public-i18n-bidi@w3.org
- Message-ID: <AANLkTimdD-hPKv_s-gvPOfMxGsBt214cMmEHLZdaiKB7@mail.gmail.com>
Agreed. -- Ehsan <http://ehsanakhgari.org/> On Thu, Nov 25, 2010 at 5:25 AM, Aharon (Vladimir) Lanin <aharon@google.com>wrote: > It seems to me that since scrollbar position is legitimately out of scope > for both CSS and HTML, we need to cover it in a new W3C document of > "recommendations" for user agent implementors. > > Aharon > > > On Thu, Nov 25, 2010 at 8:49 AM, Ehsan Akhgari <ehsan@mozilla.com> wrote: > >> I'm not positive that this would get accepted into the CSS spec. There >> are user agents today which do not use scrollbars as scrolling mechanisms, >> so I honestly am rethinking whether this makes sense as a CSS proposal at >> all... >> >> -- >> Ehsan >> <http://ehsanakhgari.org/> >> >> >> >> On Tue, Nov 23, 2010 at 7:04 PM, CE Whitehead <cewcathar@hotmail.com>wrote: >> >>> >>> Hi, I wish there could be something in css. >>> > 3.11 A page's overall vertical scrollbar should be on the "end" side >>> relative to the user agent >>> > chrome direction >>> > Bug 10825 filed on HTML5. >>> > Proposes specifying that the user agent window's overall vertical >>> scrollbar should be located >>> > independent of the direction of any page element, despite being >>> otherwise controlled by the >>> > style of thebody element. >>> > Rejected as out-of-scope: “The HTML spec doesn't even require that >>> there be a window in the >>> > first place, let alone a scroll bar. Plus, user interface decisions are >>> explicitly left up to >>> > user agents since they represent quality-of-implementation issues and >>> not interoperability >>> > issues.” >>> > Close the bug? >>> > It appears likely that a proposal to add this to the CSS spec would >>> also be rejected, since “CSS> explicitly mentions only a *scrolling >>> mechanism* and considers out-of-scope how that mechanism >>> > is implemented. It could be scroll bars, or a little panner map in the >>> corner, arrow buttons >>> > along each edge of the box, or a joystick control with no on-screen >>> representation, or something >>> > else.” >>> >>> ME: However, but I am not the one to decide this, I can see the vertical >>> scrollbar's alignment as a possible future css value for the overflow >>> attribute -- overflow: scrollleft ; overflow: scrollright (or this would >>> have to be verticaloverflow maybe? Of course scrollleft and scrollright >>> would only apply to vertical overflow obviously so no need to specify >>> vertical). Is this out of scope? >>> >>> Best, >>> --C. E. Whitehead >>> cewcathar@hotmail.com >>> >>> >>> > From: aharon@google.com >>> > Date: Tue, 16 Nov 2010 05:30:30 -0800 >>> > To: public-i18n-bidi@w3.org >>> > Subject: Implementation status of "Additional Requirements for Bidi in >>> HTML" >>> > >>> > Here is an implementation status >>> > document summarizing >>> > the status of each proposal. I will continue to update it as the status >>> > continues to change. >>> > >>> > If some part of the status is not to your liking, you are most welcome >>> > to contribute to the discussion on the various bugs and threads linked >>> > by the document while it is still possible to change things. Or, if you >>> > can try to get a consensus here on public-i18n-bidi first. >>> > >>> > Regards, >>> > Aharon >>> >> >> >
Received on Thursday, 25 November 2010 23:14:26 UTC