Upgrading Firefox to any version above 143 causes incorrect positioning of the CodeMirror autosuggestions dropdown.
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: shaurya064, Unassigned)
Details
Attachments
(1 file)
|
89.99 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36
Steps to reproduce:
- Upgrade Firefox from version 143 to 144.
- Use CodeMirror with the autosuggestions / autocompletion component.
- Observe that CodeMirror detects a transform on a parent element even though no such transform exists or was previously detected.
Actual results:
Firefox should preserve the previous behavior (as in version 143), where no transform is erroneously detected and the dropdown correctly remains position: fixed. Works fine on chrome as well.
Expected results:
The autosuggestions dropdown should remain position: fixed as it did in Firefox 143, and no false transform detection should occur.
| Reporter | ||
Comment 1•12 hours ago
|
||
The library if it detects a transform on one of the parents changes the dropdown position from fixed to absolute causing it to not behave as intended.
| Reporter | ||
Comment 2•12 hours ago
|
||
The library if it detects a transform on one of the parents changes the dropdown position from fixed to absolute causing it to not behave as intended.
| Reporter | ||
Comment 3•12 hours ago
|
||
The library if it detects a transform on one of the parents changes the dropdown position from fixed to absolute causing it to not behave as intended.
| Reporter | ||
Comment 4•12 hours ago
|
||
| Reporter | ||
Comment 5•12 hours ago
|
||
| Reporter | ||
Comment 6•12 hours ago
|
||
(In reply to Shaurya Sharma from comment #3)
The library if it detects a transform on one of the parents changes the dropdown position from fixed to absolute causing it to not behave as intended.
Comment 7•11 hours ago
|
||
Removing security flag again as this is not a security issue.
Comment 8•11 hours ago
|
||
Assuming that bug 2003918 is more accurate than this one, duping forward, I guess?
Description
•