Closed
Bug 454997
Opened 16 years ago
Closed 16 years ago
<body contenteditable="true"> exposed incorrectly
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: surkov)
References
Details
(Keywords: access)
Attachments
(1 file, 4 obsolete files)
8.19 KB,
patch
|
MarcoZ
:
review+
aaronlev
:
review+
|
Details | Diff | Splinter Review |
The nsDocumentAccessible and its descendants should be exposing EDITABLE and not be exposing READONLY.
Flags: wanted1.9.1?
Reporter | ||
Comment 1•16 years ago
|
||
Filed bug 455695 on tabbing issue with this -- both bugs affect screen reader support for Gmail.
Assignee | ||
Comment 2•16 years ago
|
||
1) expose edtiable state on document if body is contenteditable 2) merge getDOMElementFor and getRoleContent
Assignee: nobody → surkov.alexander
Status: NEW → ASSIGNED
Attachment #339744 -
Flags: review?(aaronleventhal)
Assignee | ||
Updated•16 years ago
|
Attachment #339744 -
Flags: review?(marco.zehe)
Updated•16 years ago
|
Attachment #339744 -
Flags: review?(marco.zehe) → review+
Comment 3•16 years ago
|
||
Comment on attachment 339744 [details] [diff] [review] patch A few nits: > const STATE_SELECTABLE = nsIAccessibleStates.STATE_SELECTABLE; > const STATE_SELECTED = nsIAccessibleStates.STATE_SELECTED; >+const STATE_READONLY = nsIAccessibleStates.STATE_READONLY; Please keep these in alphabetical order. >+https://bugzilla.mozilla.org/show_bug.cgi?id=442648 Please adjust the bug number. >+ <title>nsIAccessible textboxes chrome tests</title> Please adjust the title. >+ alert(getStringStates(document)); This is a debug alert, right? It would otherwise halt the test. Please remove if this is not intentional. >+ <a target="_blank" href="https://bugzilla.mozilla.org/show_bug.cgi?id=442648">Mozilla Bug 442648</a> Please adjust the bug number (see above).
Assignee | ||
Comment 4•16 years ago
|
||
with Marco's comments
Attachment #339744 -
Attachment is obsolete: true
Attachment #339747 -
Flags: review?(aaronleventhal)
Attachment #339744 -
Flags: review?(aaronleventhal)
Reporter | ||
Comment 5•16 years ago
|
||
Comment on attachment 339747 [details] [diff] [review] patch2 Alex, are you sure GetRoleContent() was never called on a text node before? Now it's going to return the element parent for that. I'm not confident that this won't change role/name/state/relation/attributes etc. for text accessibles. Wouldn't it be better to just change GetDOMElementFor() and leave GetRoleContent() alone?
Attachment #339747 -
Flags: review?(aaronleventhal)
Assignee | ||
Comment 6•16 years ago
|
||
I tend to agree, text nodes shouldn't grab the role from parent element.
Attachment #339747 -
Attachment is obsolete: true
Attachment #340061 -
Flags: review?(aaronleventhal)
Reporter | ||
Updated•16 years ago
|
Attachment #340061 -
Flags: review?(aaronleventhal) → review+
Comment 7•16 years ago
|
||
Alexander, is this ready to go in anytime soon?
Assignee | ||
Comment 8•16 years ago
|
||
checked in http://hg.mozilla.org/mozilla-central/rev/8fe1cd2d3c66
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Flags: wanted1.9.1?
Resolution: --- → FIXED
Assignee | ||
Updated•16 years ago
|
Flags: in-testsuite+
Comment 9•16 years ago
|
||
Verified fixed in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1pre) Gecko/20080927033433 Minefield/3.1b1pre
Status: RESOLVED → VERIFIED
Comment 10•16 years ago
|
||
Had to back this one out because in addition to the Thunderbird message composition window bug, it causes crashes like bp-7dde0c9e-8cb5-11dd-aa40-001cc45a2ce4, making Firefox virtually unusable.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Comment 11•16 years ago
|
||
>diff --git a/accessible/src/base/nsAccessibilityUtils.cpp b/accessible/src/base/nsAccessibilityUtils.cpp > >+ nsCOMPtr<nsIDOMHTMLDocument> htmlDoc(do_QueryInterface(node)); >+ if (htmlDoc) { >+ nsCOMPtr<nsIDOMHTMLElement> bodyElement; >+ htmlDoc->GetBody(getter_AddRefs(bodyElement)); >+ CallQueryInterface(bodyElement, element); This last line is what fails. Seems the bodyElement is not always valid.
Assignee | ||
Comment 12•16 years ago
|
||
Attachment #340061 -
Attachment is obsolete: true
Attachment #342193 -
Flags: review?(aaronleventhal)
Assignee | ||
Updated•16 years ago
|
Attachment #342193 -
Flags: review?(marco.zehe)
Comment 13•16 years ago
|
||
Alex, could you put new patch here since after your checkin to bug 457219, this one no longer applies cleanly. Thanks!
Assignee | ||
Comment 14•16 years ago
|
||
up to dated to the trunk
Attachment #342193 -
Attachment is obsolete: true
Attachment #342206 -
Flags: review?(marco.zehe)
Attachment #342193 -
Flags: review?(marco.zehe)
Attachment #342193 -
Flags: review?(aaronleventhal)
Assignee | ||
Updated•16 years ago
|
Attachment #342206 -
Flags: review?(aaronleventhal)
Comment 15•16 years ago
|
||
Comment on attachment 342206 [details] [diff] [review] patch5 1. No crashes any more as far as I can see. My testcases that produced crashes with the first checked-in patch no longer reproduce. Great work! 2. Composition rich edit in GMail now exposes editable extended state. Great! Question: In test_nsIAccessible_editablebody.html, you give the body element an ID of "body". But you never use it. Is this on purpose, or did you originally plan to use it and then forgot to remove it? You can leave it if you wish, I just noticed it and thought I'd ask. r=me
Attachment #342206 -
Flags: review?(marco.zehe) → review+
Reporter | ||
Updated•16 years ago
|
Attachment #342206 -
Flags: review?(aaronleventhal) → review+
Assignee | ||
Comment 16•16 years ago
|
||
(In reply to comment #15) > Question: In test_nsIAccessible_editablebody.html, you give the body element an > ID of "body". But you never use it. Is this on purpose, or did you originally > plan to use it and then forgot to remove it? You can leave it if you wish, I > just noticed it and thought I'd ask. yes, eventually I forgot to remove it. thanks.
Assignee | ||
Comment 17•16 years ago
|
||
checked in, http://hg.mozilla.org/mozilla-central/rev/851c5da59738
Assignee | ||
Updated•16 years ago
|
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•