[Webkit-unassigned] [Bug 33923] REGRESSION (Safari 4): AXValueChanged no longer sent for text area scrollbars

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jan 20 16:47:10 PST 2010


https://bugs.webkit.org/show_bug.cgi?id=33923





--- Comment #4 from Beth Dakin <bdakin at apple.com>  2010-01-20 16:47:10 PST ---
I will update my patch to fix all of the things you mentioned, but I want to
respond to you last comment in the meantime.

> 
> Is it really right for these all to be empty and zero in this way? Shouldn’t
> the scrollbar be a child of the accessibility object representing the container
> it scrolls or something?

There are three options for the empty-and-zero functions thing:

1. They are empty and zero.
2. I make it so those functions are no longer pure virtual, and therefore, they
have no implementation in AccessibilityScrollbar.
3. They return real values. 

#3 may seem obviously right to you, but it was not to me. To my knowledge,
scrollbars in accessibility only need to send out this notification and
potentially report on their placement (hence the implementation of
valueForRange() in the class), so they don't need to report on their size or
anything. I arbitrarily selected between the three options because there was no
clear winner to me, but I am open to doing it a different way.

Since, as I explained above, to my knowledge scrollbars do not need to do
anything else in accessibility besides send this notification, I did not make
them a child of the container it scrolls. I considered doing it that way, but a
renderer for the container is not available in Scrollbar::scroll(), so it
didn't make sense to me to find a spot where the renderer is available since I
don't know of any value of having the scrollbar be a child of the container it
scrolls.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list