To assist in triaging comprehensive-webcompat bugs, based on whether they're scheduled or not: Based on impact here, I think it's safe to say that this is one of our highest-priority layout webcompat bugs, but it's also probably high-complexity if I'm remembering things correctly, so I don't know that we can commit to having it fixed anytime soon. But I think it's safe to say that we should plan to fix this by the end of the year (which is pretty far out). Hence: setting `platform-scheduled:2025-12-31` to take this off of the unscheduled-high-priroity-webcompat-bugs list.
Bug 489100 Comment 35 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
To assist in triaging comprehensive-webcompat bugs, based on whether they're scheduled or not: Based on impact here, I think it's safe to say that this is one of our highest-priority layout webcompat bugs, but it's also probably high-complexity if I'm remembering things correctly, so I don't know that we can commit to having it fixed anytime soon. But I think it's safe to say that we should plan to fix this by the end of the year (which is pretty far out). Hence: setting `platform-scheduled:2025-12-31` to take this off of the unscheduled-high-priority-webcompat-bugs list.