Emilio Cobos Álvarez

That doesn't work for descendants of display: none elements.

See https://github.com/webcompat/web-bugs/issues/59717#issuecomment-726019954. How is the canvas size determined?

Given that if I spoof the user-agent as Chrome it works correctly, it seems like some UA-sniffing issue. These bits look related: https://github.com/ONLYOFFICE/sdkjs/blob/4c25a716cd5832e854518ff70780ee27138d56a1/common/browser.js#L187

@sefeng211 does the performance team have any concern with this?

Hmm, after re-fetching and rebasing on top of central, it went away :/ ``` $ g fetch mozilla From hg::https://hg.mozilla.org/mozilla-unified - [deleted] (none) -> mozilla/branches/default/b379b56bf47cdfb9149b134dd1f9cd4850d72cfc Reading 29 changesets Reading and...

This is on 1f5816249c4dfccedfe5f79682f1fc117d5a92df (hg: 0e384d802c84057a296e06a6b05f0326ed8c46e3) plus a few patches, attached below. [patches.bundle.zip](https://github.com/glandium/git-cinnabar/files/9729429/patches.bundle.zip)

Yeah, I fetch from try relatively frequently (e.g., my patch fails on macOS, I fix it on my Mac, push to try again and update the patch stack on my...

I see. Yeah I've pushed test fixes to autoland (with sheriff's permission), so that explains that divergence.

> The site is using webkit specific rules to make the number spinner go away and [it's not supported in Firefox](https://bugzilla.mozilla.org/show_bug.cgi?id=1355574): > > ```css > input::-webkit-inner-spin-button, input::-webkit-outer-spin-button { appearance: none;...

Gah, yeah, got tricked by the autocomplete, sorry!