Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fido2-page-script-delay-append-mv2.js still breaking styles in Firefox #11428

Closed
1 task done
Jamie0 opened this issue Oct 5, 2024 · 2 comments
Closed
1 task done

fido2-page-script-delay-append-mv2.js still breaking styles in Firefox #11428

Jamie0 opened this issue Oct 5, 2024 · 2 comments
Assignees
Labels
browser Browser Extension bug

Comments

@Jamie0
Copy link

Jamie0 commented Oct 5, 2024

Steps To Reproduce

This affects screens in a commercial web application I maintain. I can provide testing credentials to project maintainers. Tested in Firefox, 2024.9.1.

  1. Log into application
  2. About five seconds later, all the styles are removed

Expected Result

tags should not be removed from the page by the extension

Actual Result

Some and <style /> tags, which are not managed by the extension, are removed from the page.

Screenshots or Videos

image image

Additional Context

Part of the issue is that the document.head element doesn't exist at the time fido2-page-script-delay-append-mv2.js executes.

This causes the <script /> tag to be created as the first child under <html />, and remain there for most of the page load.

The module loading framework that we use expects document.documentElement[0] to be document.head. This results in <link /> and <script /> tags being inserted into the fido2 script tag, which are then removed when the script tag is deleted.

This is related to #10830 and #11304. Although I'm testing in the current version (2024.9.1), it looks like the code in the main branch is still susceptible to this.

Operating System

Windows, macOS, Linux

Operating System Version

No response

Web Browser

Firefox

Browser Version

No response

Build Version

2024.9.1

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@Krychaz
Copy link
Member

Krychaz commented Oct 7, 2024

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

@cagonzalezcs cagonzalezcs self-assigned this Oct 7, 2024
@cagonzalezcs
Copy link
Contributor

Resolved with the changed from #11444

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser Browser Extension bug
Projects
None yet
Development

No branches or pull requests

3 participants