Spun off bug 1256706. Twitter used to do a CSS change from position:absolute; to position:relative; when focus changed from one tweet to the next, see bug 1256706 comment #4 and dholbert's analysis in bug 1256706 comment #5. Implement a solution on the accessibility APIs side as suggested in bug 1256706 comment #7: > Also we could try to make the accessible tree updates smarter, like if a > frame type of a DOM node wasn't changed during frames reconstruction then no > accessible update should be required. This check shouldn't be very expensive. Alex, you also said you had a prototype working. Could you finish this on this bug?
3 years ago
(In reply to Marco Zehe (:MarcoZ) from comment #0) > Alex, you also said you had a prototype working. Could you finish this on > this bug? thanks for filing it, I'll see what I can do
2 years ago
Priority: -- → P3
let's move this one out off the backlog, it should be considered to be fixed asap.
Priority: P3 → P2
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.