Depends on the results of T143334 (if we have to remove the code then this task is invalid).
We should change it to reject known problematic UAs instead of approving a few ones for future proofness.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Jhernandez | T143334 [SPIKE: 2hrs] Should we remove supportsPositionFixed and Skin#setupPositionFixedEmulation? | |||
| Declined | None | T143337 Fix Browser#supportsPositionFixed |
Event Timeline
Comment Actions
I'm not sure, if we have a list of the known problematic browsers, then a 2 sounds good. If not, then a 5 for finding those browsers and testing this feature against those browsers (qUnit tests).
Comment Actions
This is fixing supportsPositionFixed to work on the codebase, but in any case this.on('scroll' in the skin would still not trigger, so additional tasks will be needed to fix the emulation and test it in old devices if necessary.