Bug 1819239 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Hi Masayuki,

Per the build range in comment 1, is it possible that this assertion is caused by Bug 1792386 or Bug  1792386?

In the callstack `#13 0x7f8bdf5e57ba in mozilla::AccessibleCaret::SetPosition()`, there are guards to prevent layout flush calls in `AccessibleCaretManager` in https://searchfox.org/mozilla-central/rev/aa3ccd258b64abfd4c5ce56c1f512bc7f65b844c/layout/base/AccessibleCaretManager.cpp#745-752, but it looks like `dom::Element::SetAttr` can still trigger layout flush in editor via a callback. I wonder whether we can avoid that.
Revision 1 by
on 
Hi Masayuki,

Per the build range in comment 1, is it possible that this assertion is caused by Bug 1792386?

In the callstack `#13 0x7f8bdf5e57ba in mozilla::AccessibleCaret::SetPosition()`, there are guards to prevent layout flush calls in `AccessibleCaretManager` in https://searchfox.org/mozilla-central/rev/aa3ccd258b64abfd4c5ce56c1f512bc7f65b844c/layout/base/AccessibleCaretManager.cpp#745-752, but it looks like `dom::Element::SetAttr` can still trigger layout flush in editor via a callback. I wonder whether we can avoid that.

Back to Bug 1819239 Comment 3