(In reply to Oana Arbuzov [:oanaarbuzov] from comment #9) > Based on the reduced html test, the button is displayed correctly on Firefox, but broken on Chrome. > https://prnt.sc/8G6j3sKdOrqT Yeah, that's expected (and not a Chrome bug). To clarify -- the reduced testcase was reduced from the HTML that blogger was sending Firefox; it's not expected to work in Chrome. (Blogger was sending Firefox and Chrome different vendor-prefixed syntax, which was part of the problem here; and the reduced testcase is from what they were sending us.) See comment 4. It looks like the commit that caused the behavior change here (bug 1337655) was backed out and wontfix'ed, per comment 7. Before that backout, Firefox would've rendered the attached reduced-testcase as "bad", which is why this bug was filed. But it's back to fine ever since then. (Also, maybe Blogger has changed? It doesn't look like the original screenshot anymore, though I may not be looking at the right page.) In any case, this should be fine now, since we backed out bug 1337655.
Bug 1512577 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Oana Arbuzov [:oanaarbuzov] from comment #9) > Based on the reduced html test, the button is displayed correctly on Firefox, but broken on Chrome. > https://prnt.sc/8G6j3sKdOrqT Yeah, that's expected (and not a Chrome bug). To clarify -- the reduced testcase was reduced from the HTML that blogger was sending Firefox; it's not expected to work in Chrome. (Blogger was sending Firefox and Chrome different vendor-prefixed syntax, which was part of the problem here; and the reduced testcase is from what they were sending us.) See comment 4. It looks like the commit that caused the behavior change here (bug 1337655) was backed out and wontfix'ed, per comment 7. Before that backout, Firefox would've rendered the attached reduced-testcase as "bad", which is why this bug was filed. But things should be back to being fine ever since the backout. (Also, independently, maybe Blogger has changed their styling/design? It doesn't look like the original screenshot anymore, though I may not be looking at the right page.) In any case, this should be fine now, since we backed out bug 1337655.