Setting focus on div with Mozilla

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Arne

    #1

    Setting focus on div with Mozilla

    During testing <div style="overflow :auto;"> in CSS I noticed the
    mousewheel would work in Mozilla only after I made a <a href="#">some
    text</a> link and clicked on that, within the div.

    It appears as if Mozilla needs to have the focus set on that div in
    order for the mousewheel to work. That's all that link does. The
    mousewheel works perfectly in IE without the link. It scrolls the div
    even if there is a scrollbar on the page.

    Is there any reason (according to standard or something else) why
    Mozilla can't scroll without setting the focus, and is there any other
    way to do it.

    --
    /Arne

    Top posters will be ignored. Quote the part you
    are replying to, no more and no less! And don't
    quote signatures, thank you.
  • Spartanicus

    #2
    Re: Setting focus on div with Mozilla

    Arne <invalid@domain .invalid> wrote:
    [color=blue]
    >During testing <div style="overflow :auto;"> in CSS I noticed the
    >mousewheel would work in Mozilla only after I made a <a href="#">some
    >text</a> link and clicked on that, within the div.
    >
    >It appears as if Mozilla needs to have the focus set on that div in
    >order for the mousewheel to work. That's all that link does. The
    >mousewheel works perfectly in IE without the link. It scrolls the div
    >even if there is a scrollbar on the page.[/color]

    Now consider a keyboard user, for them your scrolling thingy is also a
    nightmare to use. Which is why creating any scrollable viewport within
    the main viewport is considered a usability no-no.

    --
    Spartanicus

    Comment

    • Arne

      #3
      Re: Setting focus on div with Mozilla

      Once upon a time *Spartanicus* wrote:
      [color=blue]
      > Arne <invalid@domain .invalid> wrote:
      >[color=green]
      >>During testing <div style="overflow :auto;"> in CSS I noticed the
      >>mousewheel would work in Mozilla only after I made a <a href="#">some
      >>text</a> link and clicked on that, within the div.
      >>
      >>It appears as if Mozilla needs to have the focus set on that div in
      >>order for the mousewheel to work. That's all that link does. The
      >>mousewheel works perfectly in IE without the link. It scrolls the div
      >>even if there is a scrollbar on the page.[/color]
      >
      > Now consider a keyboard user, for them your scrolling thingy is also a
      > nightmare to use. Which is why creating any scrollable viewport within
      > the main viewport is considered a usability no-no.
      >[/color]

      Read again what I wrote: I'm *testing* it but have so far no intention
      or need to use it.

      Why am testing? That's because there is sites 'out there' that use
      scrolling div's and I discovered that I could not use my mousewheel to
      scroll when I used Mozilla. In IE it works by placing the cursor
      anywhere inside the div.

      With the link inside the div the scrolling works on IE even for
      keyboard users, even if it may be a nightmare the keys takes you thru
      the links and when the link in the div is focused you can scroll it
      with the arrow keys.

      So my question still stands open, why does that work in other browsers
      and is there a way (others than I described abow) to make it work? But
      remember now, I know about the "usability no-no" but I would like to
      know since I would like to use the scrolling on sites where they use
      the scrolling div's.

      If the "usability no-no" is the reason why standard compliant (is it
      the right word?) browser don't support it, then why support the
      scrolling divs at all?

      --
      /Arne

      Top posters will be ignored. Quote the part you
      are replying to, no more and no less! And don't
      quote signatures, thank you.

      Comment

      • Spartanicus

        #4
        Re: Setting focus on div with Mozilla

        Arne <invalid@domain .invalid> wrote:
        [color=blue]
        >I would like to use the scrolling on sites where they use
        >the scrolling div's.[/color]

        If that is the case then the question belongs in a group specific to
        your browser, not a group devoted to www authoring such as this.

        --
        Spartanicus

        Comment

        • Stan Brown

          #5
          Re: Setting focus on div with Mozilla

          On Sun, 17 Jul 2005 20:22:11 GMT, Spartanicus
          <invalid@invali d.invalid> wrote:
          [color=blue]
          >Now consider a keyboard user, for them your scrolling thingy is also a
          >nightmare to use. Which is why creating any scrollable viewport within
          >the main viewport is considered a usability no-no.[/color]

          I never thought about that before, in terms of scrollable tables. I
          presume the same would apply?

          --
          Stan Brown, Oak Road Systems, Tompkins County, New York, USA
          DRAGON222 menjadi pusat resmi terunggul Sportsbook Digital. Sistem cepat respon, tampilan sangat lancar anti lag, dan kemungkinan menang terjadi pada tekad kuat anda.

          HTML 4.01 spec: http://www.w3.org/TR/html401/
          validator: http://validator.w3.org/
          CSS 2.1 spec: http://www.w3.org/TR/CSS21/
          validator: http://jigsaw.w3.org/css-validator/
          Why We Won't Help You:

          Comment

          • Sander Tekelenburg

            #6
            Re: Setting focus on div with Mozilla

            In article
            <kefld1pget0r56 et5nufc8m69f784 7pora@news.spar tanicus.utvinte rnet.ie>,
            Spartanicus <invalid@invali d.invalid> wrote:
            [color=blue]
            > Arne <invalid@domain .invalid> wrote:
            >[color=green]
            > >During testing <div style="overflow :auto;"> in CSS I noticed the
            > >mousewheel would work in Mozilla only after I made a <a href="#">some
            > >text</a> link and clicked on that, within the div.
            > >
            > >It appears as if Mozilla needs to have the focus set on that div in
            > >order for the mousewheel to work.[/color][/color]

            Makes sense, doesn't it? I think every GUI I ever used required focus on
            an object before that object can be manipulated.
            [color=blue][color=green]
            > > That's all that link does.[/color][/color]

            Sounds like Mozilla doesn't offer a way to activate the object (your
            DIV), but due to its capability of setting focus to *hyperlinks* you get
            the result you see.

            I'd consider this bad UI design.
            [color=blue][color=green]
            > > The
            > >mousewheel works perfectly in IE without the link. It scrolls the div
            > >even if there is a scrollbar on the page.[/color][/color]

            I presume you mean you can set focus to the DIV somehow, even when it
            doesn't contain a hyperlink? I can't imagine it 'just works' - then how
            would IE know when to scroll the viewport and when a child?
            [color=blue]
            > Now consider a keyboard user, for them your scrolling thingy is also a
            > nightmare to use. Which is why creating any scrollable viewport within
            > the main viewport is considered a usability no-no.[/color]

            I don't see the logic there. It's up to the browser vendor to ensure the
            user can access whatever object he may want/need to access in whatever
            way the user might want that.

            I don't see specific browsers' limitations as a reason to 'dumb down' a
            site (which would mean dumbing it down for everybody, including those
            who use a more powerful browser).

            --
            Sander Tekelenburg, <http://www.euronet.nl/%7Etekelenb/>

            Comment

            • RobG

              #7
              Re: Setting focus on div with Mozilla

              Sander Tekelenburg wrote:[color=blue]
              > In article
              > <kefld1pget0r56 et5nufc8m69f784 7pora@news.spar tanicus.utvinte rnet.ie>,
              > Spartanicus <invalid@invali d.invalid> wrote:
              >
              >[color=green]
              >>Arne <invalid@domain .invalid> wrote:
              >>
              >>[color=darkred]
              >>>During testing <div style="overflow :auto;"> in CSS I noticed the
              >>>mousewheel would work in Mozilla only after I made a <a href="#">some
              >>>text</a> link and clicked on that, within the div.
              >>>
              >>>It appears as if Mozilla needs to have the focus set on that div in
              >>>order for the mousewheel to work.[/color][/color]
              >
              >
              > Makes sense, doesn't it? I think every GUI I ever used required focus on
              > an object before that object can be manipulated.[/color]

              Your use of 'focus' is out of context - the OP was using focus in the
              sense of DOM elements. A DIV element does not have a focus property or
              method, and therefore can't have focus in the that sense.

              Mouse wheel scrolling and DOM element focus have no direct relationship.
              There is no W3 standard that defines what the document's response
              should be to any mouse-scroll event.

              Browser developers are therefore left to their own devices as to how to
              interpret mouse-scrolling, which is no doubt responsible for the fact
              that the response of various browsers to mouse-wheel events is inconsistent.
              [color=blue]
              >[color=green][color=darkred]
              >>>That's all that link does.[/color][/color]
              >
              >
              > Sounds like Mozilla doesn't offer a way to activate the object (your
              > DIV), but due to its capability of setting focus to *hyperlinks* you get
              > the result you see.
              >
              > I'd consider this bad UI design.[/color]

              IE needs the suggested A element in order to provide keyboard navigation
              of a scrolling div too. No doubt you also consider that bad UI design.
              [color=blue]
              >[color=green][color=darkred]
              >>>The
              >>>mousewheel works perfectly in IE without the link. It scrolls the div
              >>>even if there is a scrollbar on the page.[/color][/color]
              >
              >
              > I presume you mean you can set focus to the DIV somehow, even when it
              > doesn't contain a hyperlink? I can't imagine it 'just works' - then how
              > would IE know when to scroll the viewport and when a child?[/color]

              The OP means that in IE if you put the cursor over the div then it
              scrolls (if it can) in response to mouse wheel scrolling, not the page.
              You can't 'set focus' on a div.

              IE 'knows' when to scroll because it has been programmed to provide
              certain behaviour. If the cursor is over the page, the page is
              scrolled. If a scrollable div is below the cursor, the div is scrolled.
              If it can't be scrolled in the direction indicated, the page is
              scrolled if possible.
              [color=blue]
              >[color=green]
              >>Now consider a keyboard user, for them your scrolling thingy is also a
              >>nightmare to use. Which is why creating any scrollable viewport within
              >>the main viewport is considered a usability no-no.[/color]
              >
              >
              > I don't see the logic there. It's up to the browser vendor to ensure the
              > user can access whatever object he may want/need to access in whatever
              > way the user might want that.[/color]

              And it's up to developers to present usable pages. Developers should
              not depend on non-standard, browser-dependent behaviour to allow access
              to content.
              [color=blue]
              >
              > I don't see specific browsers' limitations as a reason to 'dumb down' a
              > site (which would mean dumbing it down for everybody, including those
              > who use a more powerful browser).[/color]

              So dysfunctional pages that prevent access to parts of their content for
              certain users are OK? Those users being ones dependent on keyboard or
              other non-pointing-device navigation.

              I think you are out of step with one of the fundamental tenets of web
              design. Restricting accessibility for no good reason is, in some
              jurisdictions,i n breach of laws regarding accessibility.


              --
              Rob

              Comment

              • Arne

                #8
                Re: Setting focus on div with Mozilla

                Once upon a time *Spartanicus* wrote:
                [color=blue]
                > Arne <invalid@domain .invalid> wrote:
                >[color=green]
                >>I would like to use the scrolling on sites where they use
                >>the scrolling div's.[/color]
                >
                > If that is the case then the question belongs in a group specific to
                > your browser, not a group devoted to www authoring such as this.[/color]

                Did that, but no response so far. I'll guess they know Mozilla but
                maybe not to much CSS? :)

                --
                /Arne

                Top posters will be ignored. Quote the part you
                are replying to, no more and no less! And don't
                quote signatures, thank you.

                Comment

                • Arne

                  #9
                  Re: Setting focus on div with Mozilla

                  Once upon a time *Sander Tekelenburg* wrote:
                  [color=blue]
                  > In article
                  > <kefld1pget0r56 et5nufc8m69f784 7pora@news.spar tanicus.utvinte rnet.ie>,
                  > Spartanicus <invalid@invali d.invalid> wrote:
                  >[color=green]
                  >> Arne <invalid@domain .invalid> wrote:
                  >>[color=darkred]
                  >> >During testing <div style="overflow :auto;"> in CSS I noticed the
                  >> >mousewheel would work in Mozilla only after I made a <a href="#">some
                  >> >text</a> link and clicked on that, within the div.
                  >> >
                  >> >It appears as if Mozilla needs to have the focus set on that div in
                  >> >order for the mousewheel to work.[/color][/color]
                  >
                  > Makes sense, doesn't it? I think every GUI I ever used required focus on
                  > an object before that object can be manipulated.[/color]

                  True of course. :)
                  The question is why moving the cursor on the object don't set the
                  focus, as in IE.
                  [color=blue][color=green][color=darkred]
                  >> > That's all that link does.[/color][/color]
                  >
                  > Sounds like Mozilla doesn't offer a way to activate the object (your
                  > DIV), but due to its capability of setting focus to *hyperlinks* you get
                  > the result you see.
                  >
                  > I'd consider this bad UI design.
                  >[color=green][color=darkred]
                  >> > The
                  >> >mousewheel works perfectly in IE without the link. It scrolls the div
                  >> >even if there is a scrollbar on the page.[/color][/color]
                  >
                  > I presume you mean you can set focus to the DIV somehow, even when it
                  > doesn't contain a hyperlink? I can't imagine it 'just works' - then how
                  > would IE know when to scroll the viewport and when a child?[/color]

                  With IE the focus is set just by moving the cursor to the div, no
                  clicking needed. As long as there is scrollable content in the div the
                  focus stays, then the viewport is scrolled if there is a scrollbar for
                  the viewport.

                  It seams that with IR the 'point' is where you have the cursor when
                  you start scrolling. With the link in the div it works in IE for
                  keyboard users also, but not in Mozilla even if the focus is moved to
                  the link with keys.

                  --
                  /Arne

                  Top posters will be ignored. Quote the part you
                  are replying to, no more and no less! And don't
                  quote signatures, thank you.

                  Comment

                  • Sander Tekelenburg

                    #10
                    Re: Setting focus on div with Mozilla

                    In article <3k197hFs6vsaU1 @individual.net >,
                    Arne <invalid@domain .invalid> wrote:

                    [...]
                    [color=blue]
                    > The question is why moving the cursor on the object don't set the
                    > focus, as in IE.[/color]

                    If you care, ask the Mozilla developers for such a feature. (And say
                    "hover over the object", so they'll understand what you mean ;))

                    [...]
                    [color=blue][color=green]
                    > > I can't imagine it 'just works' - then how
                    > > would IE know when to scroll the viewport and when a child?[/color]
                    >
                    > With IE the focus is set just by moving the cursor to the div, no
                    > clicking needed.[/color]

                    Ah, I see. I hadn't understood that earlier.
                    [color=blue]
                    > As long as there is scrollable content in the div the
                    > focus stays, then the viewport is scrolled if there is a scrollbar for
                    > the viewport.[/color]

                    I see. Sounds like it might be a useful implementation.
                    [color=blue]
                    > [...] With the link in the div it works in IE for
                    > keyboard users also[/color]

                    How? How do you set that focus with the keyboard in IE?

                    --
                    Sander Tekelenburg, <http://www.euronet.nl/%7Etekelenb/>

                    Comment

                    • Spartanicus

                      #11
                      Re: Setting focus on div with Mozilla

                      Arne <invalid@domain .invalid> wrote:
                      [color=blue][color=green][color=darkred]
                      >>>I would like to use the scrolling on sites where they use
                      >>>the scrolling div's.[/color]
                      >>
                      >> If that is the case then the question belongs in a group specific to
                      >> your browser, not a group devoted to www authoring such as this.[/color]
                      >
                      >Did that, but no response so far. I'll guess they know Mozilla but
                      >maybe not to much CSS? :)[/color]

                      Whether or not you can use divs with a scrollbar in Mozilla has got
                      nothing to do with CSS.

                      --
                      Spartanicus

                      Comment

                      • Sander Tekelenburg

                        #12
                        Re: Setting focus on div with Mozilla

                        In article <0uHCe.9$pF3.19 32@news.optus.n et.au>,
                        RobG <rgqld@iinet.ne t.auau> wrote:
                        [color=blue]
                        > Sander Tekelenburg wrote:[/color]

                        [...]
                        [color=blue][color=green]
                        > > I think every GUI I ever used required focus on
                        > > an object before that object can be manipulated.[/color]
                        >
                        > Your use of 'focus' is out of context - the OP was using focus in the
                        > sense of DOM elements. A DIV element does not have a focus property or
                        > method, and therefore can't have focus in the that sense.[/color]

                        Yes, I considered writing "focus/select/activate" but didn't because I
                        thought it was obvious enough what I meant :)

                        But I don't see how the DOM is even relevant. If a browser presents
                        something within a scrollable area, it should offer the user useful
                        methods to interact with that. I think that's all there is to it.

                        [...]
                        [color=blue]
                        > There is no W3 standard that defines what the document's response
                        > should be to any mouse-scroll event.[/color]

                        I don't see why there should be. W3C is no UI implementation authority
                        (although here and there in theor specs they point out some obvious UI
                        things).
                        [color=blue]
                        > Browser developers are therefore left to their own devices as to how to
                        > interpret mouse-scrolling, which is no doubt responsible for the fact
                        > that the response of various browsers to mouse-wheel events is inconsistent.[/color]

                        Indeed.

                        [...]
                        [color=blue]
                        > IE needs the suggested A element in order to provide keyboard navigation
                        > of a scrolling div too. No doubt you also consider that bad UI design.[/color]

                        Yep.

                        [...]
                        [color=blue][color=green]
                        > > I don't see the logic there. It's up to the browser vendor to ensure the
                        > > user can access whatever object he may want/need to access in whatever
                        > > way the user might want that.[/color]
                        >
                        > And it's up to developers to present usable pages. Developers should
                        > not depend on non-standard, browser-dependent behaviour to allow access
                        > to content.[/color]

                        I couldn't agree more, but I don't see how it applies to this case.
                        Webpages should be HTTP- and HTML-dependant only. But if a browser
                        decides to accept a suggestion to render something with a scrollbar, it
                        should provide the user with a good mechanism to interact with that. If
                        it does not, it shouldn't have honoured that presentational suggestion
                        in the first place. The only way in which this affects "liquid design",
                        is that as an author you should anticipate that a browser might not
                        honour your suggestion to present something scrollable. Design things so
                        that in that case the usability/accessibility of the page doesn't
                        seriously degrade.
                        [color=blue][color=green]
                        > > I don't see specific browsers' limitations as a reason to 'dumb down' a
                        > > site (which would mean dumbing it down for everybody, including those
                        > > who use a more powerful browser).[/color]
                        >
                        > So dysfunctional pages that prevent access to parts of their content for
                        > certain users are OK?[/color]

                        Show me how it is the page that prevents access. As far as I can see it
                        is the browser.
                        [color=blue]
                        > Those users being ones dependent on keyboard or
                        > other non-pointing-device navigation.[/color]

                        I know. Are they dependant upon Microsoft or Mozilla too? Can't they
                        pick a browsing environment that *does* work well? If it doesn't exist,
                        can't they develop one, or pay for having one developed? Why should we
                        sit on our hands waiting for non-inventive companies to move the Web to
                        maturity?
                        [color=blue]
                        > I think you are out of step with one of the fundamental tenets of web
                        > design.[/color]

                        The only thing this has to do with webdesign is that with Web publishers
                        dumbing pages down to avoid bugs/lousy behaviour in browsers, thus
                        hiding how sad the quality of most browsers is, they're contributing to
                        browsers, and thus the Web, to remain as infantile as it is. If on the
                        other hand Web publishers would just go ahead and make use of what the
                        HTML and CSS standards have to offer, most browsers' problems would be
                        visible to everyone - browser developers would feel much more pressure
                        to start producing quality. (Would make the Web cheaper too, as Web
                        publishers wouldn't have to waste time tracking and avoiding other
                        developer's bugs.)

                        F'r instance: if Web publishers would use the LINK element en masse,
                        there wouldn't be a need anymore to copy the same functionality to the
                        BODY. By not using it, there is little incentive for browser developers
                        to 'waste' resources on such a thing.
                        [color=blue]
                        > Restricting accessibility for no good reason is, in some
                        > jurisdictions,i n breach of laws regarding accessibility.[/color]

                        A law that allows convicting one person for another's mistakes, assuming
                        such a law exists, is a bug.

                        --
                        Sander Tekelenburg, <http://www.euronet.nl/%7Etekelenb/>

                        Comment

                        • RobG

                          #13
                          Re: Setting focus on div with Mozilla

                          Sander Tekelenburg wrote:
                          [...][color=blue][color=green]
                          >>As long as there is scrollable content in the div the
                          >>focus stays, then the viewport is scrolled if there is a scrollbar for
                          >>the viewport.[/color]
                          >
                          > I see. Sounds like it might be a useful implementation.
                          >
                          >[color=green]
                          >>[...] With the link in the div it works in IE for
                          >>keyboard users also[/color]
                          >
                          >
                          > How? How do you set that focus with the keyboard in IE?
                          >[/color]

                          In most browsers, pressing the 'tab' key will move between UI features
                          that can have focus (including the address bar or location field).

                          If a scrolling div contains an element that can have focus (A, INPUT,
                          BUTTON, LABEL etc.) then after a suitable number of 'tab' presses the
                          focus moves to those elements in turn.

                          The order in which elements are visited can be controlled using the
                          'tabindex' attribute.

                          <URL:http://www.w3.org/TR/html4/interact/forms.html#adef-tabindex>

                          Once one of them has focus, the up/down arrow keys can be used to
                          scroll the div. If the scrolling does not contain any elements that
                          can have focus, it can't be scrolled with the keyboard.

                          The above behaviour occurs in Mozilla and IE.

                          --
                          Rob

                          Comment

                          • Arne

                            #14
                            Re: Setting focus on div with Mozilla

                            Once upon a time *RobG* wrote:
                            [color=blue]
                            > Sander Tekelenburg wrote:
                            > [...][color=green][color=darkred]
                            >>>As long as there is scrollable content in the div the
                            >>>focus stays, then the viewport is scrolled if there is a scrollbar for
                            >>>the viewport.[/color]
                            >>
                            >> I see. Sounds like it might be a useful implementation.
                            >>
                            >>[color=darkred]
                            >>>[...] With the link in the div it works in IE for
                            >>>keyboard users also[/color]
                            >>
                            >>
                            >> How? How do you set that focus with the keyboard in IE?
                            >>[/color]
                            >
                            > In most browsers, pressing the 'tab' key will move between UI features
                            > that can have focus (including the address bar or location field).
                            >
                            > If a scrolling div contains an element that can have focus (A, INPUT,
                            > BUTTON, LABEL etc.) then after a suitable number of 'tab' presses the
                            > focus moves to those elements in turn.
                            >
                            > The order in which elements are visited can be controlled using the
                            > 'tabindex' attribute.
                            >
                            > <URL:http://www.w3.org/TR/html4/interact/forms.html#adef-tabindex>
                            >
                            > Once one of them has focus, the up/down arrow keys can be used to
                            > scroll the div. If the scrolling does not contain any elements that
                            > can have focus, it can't be scrolled with the keyboard.
                            >
                            > The above behaviour occurs in Mozilla and IE.
                            >[/color]

                            Not totaly the same in IE and Mozilla. When the link in the div is in
                            focus, it can be scrolled with both arrow keys and mouse. With Mozilla
                            I can't scroll the div with the keys, only with the mouse and that is
                            strange. Guess I have to take it to the Moz developers :)


                            --
                            /Arne

                            Top posters will be ignored. Quote the part you
                            are replying to, no more and no less! And don't
                            quote signatures, thank you.

                            Comment

                            • RobG

                              #15
                              Re: Setting focus on div with Mozilla

                              Sander Tekelenburg wrote:[color=blue]
                              > In article <0uHCe.9$pF3.19 32@news.optus.n et.au>,
                              > RobG <rgqld@iinet.ne t.auau> wrote:
                              >[color=green]
                              >>Sander Tekelenburg wrote:[/color]
                              >
                              > [...]
                              >[color=green][color=darkred]
                              >>>I think every GUI I ever used required focus on
                              >>>an object before that object can be manipulated.[/color]
                              >>
                              >>Your use of 'focus' is out of context - the OP was using focus in the
                              >>sense of DOM elements. A DIV element does not have a focus property or
                              >>method, and therefore can't have focus in the that sense.[/color]
                              >
                              > Yes, I considered writing "focus/select/activate" but didn't because I
                              > thought it was obvious enough what I meant :)[/color]

                              Yes, 'activate' would likely have been a better word. X-Windows puts
                              'focus' on whichever window the cursor is over, even if it's in the
                              background - a feature I disliked. Keyboard input would often end up
                              in the wrong TTY session 'cos I'd move the cursor out of the way of
                              the 'current' window and accidentally give focus to a different window
                              & session.
                              [color=blue]
                              > But I don't see how the DOM is even relevant. If a browser presents
                              > something within a scrollable area, it should offer the user useful
                              > methods to interact with that. I think that's all there is to it.[/color]

                              'The browser' doesn't design web pages, people do. If a person puts
                              content into an area that *no* browser provides keyboard navigation
                              to, then that is the person's fault, not the browsers'.

                              [...]
                              But if a browser[color=blue]
                              > decides to accept a suggestion to render something with a scrollbar, it
                              > should provide the user with a good mechanism to interact with that. If
                              > it does not, it shouldn't have honoured that presentational suggestion
                              > in the first place. The only way in which this affects "liquid design",[/color]

                              OK, so you think browsers should not present scrolling divs.
                              [color=blue]
                              > is that as an author you should anticipate that a browser might not
                              > honour your suggestion to present something scrollable. Design things so
                              > that in that case the usability/accessibility of the page doesn't
                              > seriously degrade.[/color]

                              Precisely - the suggestion is don't use scrolling divs where
                              accessibility is important.

                              [...][color=blue][color=green]
                              >>So dysfunctional pages that prevent access to parts of their content for
                              >>certain users are OK?[/color]
                              >
                              > Show me how it is the page that prevents access. As far as I can see it
                              > is the browser.[/color]

                              By expecting visitors to make use of features that browsers don't
                              provide, such as the ability to scroll a scrolling div using keyboard
                              navigation only.
                              [color=blue]
                              >[color=green]
                              >>Those users being ones dependent on keyboard or
                              >>other non-pointing-device navigation.[/color]
                              >
                              >
                              > I know. Are they dependant upon Microsoft or Mozilla too? Can't they
                              > pick a browsing environment that *does* work well? If it doesn't exist,
                              > can't they develop one, or pay for having one developed? Why should we
                              > sit on our hands waiting for non-inventive companies to move the Web to
                              > maturity?[/color]

                              In the context of a special interest or intranet site, go for it. But
                              it's worth noting accessibility requirements for those sites where
                              public access is a requirement.
                              [color=blue]
                              >[color=green]
                              >>I think you are out of step with one of the fundamental tenets of web
                              >>design.[/color]
                              >
                              > The only thing this has to do with webdesign is that with Web publishers
                              > dumbing pages down to avoid bugs/lousy behaviour in browsers, thus[/color]

                              It's not a bug, the browsers work as designed and conform to the
                              relevant standards. The point on behaviour is moot - browser
                              developers have had great pressure exerted on them to follow
                              standards, they can hardly be taken to task for doing so.

                              If you don't like the standard, approach W3.org.

                              [...]

                              --
                              Rob

                              Comment

                              Working...