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
adev is broken on Firefox after xtermjs is loaded and table of contents item clicked #54894
Comments
JeanMeche
added a commit
to JeanMeche/angular
that referenced
this issue
Mar 15, 2024
With 5.4.0 `xterm` has migrated to scoped packages. We're now using `@xterm/xterm`. Fixes angular#54894
JeanMeche
added a commit
to JeanMeche/angular
that referenced
this issue
Mar 15, 2024
With 5.4.0 `xterm` has migrated to scoped packages. We're now using `@xterm/xterm`. Fixes angular#54894
JeanMeche
added a commit
to JeanMeche/angular
that referenced
this issue
Mar 15, 2024
With 5.4.0 `xterm` has migrated to scoped packages. We're now using `@xterm/xterm`. Fixes angular#54894
Hi, we appreciate you took the time to investigate the issue. |
ilirbeqirii
pushed a commit
to ilirbeqirii/angular
that referenced
this issue
Apr 6, 2024
…x. (angular#54897) With 5.4.0 `xterm` has migrated to scoped packages. We're now using `@xterm/xterm`. Fixes angular#54894 PR Close angular#54897
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
How to reproduce:
xtermjs
(either https://angular.dev/playground or scroll down on the landing page)Repro video:
https://drive.google.com/file/d/12GHRIDE3GidLv_kASuid0cA0I9euEu2v/view
xtermjs
seems to be inserting absolutely positioned elements that affect viewport width in Firefox.Related to xtermjs/xterm.js#4805
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: