(In reply to Mounir Lamouri (:mounir) from comment #75) > BTW, do we have to expose the anonymous nodes to the accessible document?
it depends, we expose them when we need them > It > seems that regarding a11y, it would be as good to simply have one element > that has some value and can be open (popup state?). I don't know much about > a11y so I might be missing some reasons why we expose those anonymous nodes. the idea is to keep a11y closer to the UI, what the user sees on the screen he hears the same by screen reader. It doesn't necessary contradicts to what you said though. I'm certain we need to have that 'Browse' button, mapping of all other controls can vary I guess. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/209509 Title: <input type=file> does not accept textual input Status in XUL + XPCOM application runner: In Progress Status in “firefox” package in Ubuntu: Won't Fix Status in “firefox-3.0” package in Ubuntu: Won't Fix Status in “firefox-3.5” package in Ubuntu: Won't Fix Bug description: Binary package hint: firefox Firefox 3 (3.0~b4+nobinonly-0ubuntu1) immediately opens a "file upload" dialog when I click on the file name field. Ff should only open this dialog if click on [Browse...]. Even after I close the dialog window I can neither input a file name directly into the field nor can I remove the file from the input field. It should be as easy editable as in firefox 2. I use Hardy amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/xulrunner/+bug/209509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
