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

bug(progress-bar): Display issue on Firefox #7606

Closed
ghost opened this issue Oct 6, 2017 · 6 comments · Fixed by #9123
Closed

bug(progress-bar): Display issue on Firefox #7606

ghost opened this issue Oct 6, 2017 · 6 comments · Fixed by #9123
Assignees
Labels
needs investigation A member of the team needs to do further investigation to determine the root cause P2 The issue is important to a large percentage of users, with a workaround

Comments

@ghost
Copy link

ghost commented Oct 6, 2017

Bug, feature request, or proposal:

Bug

What is the expected behavior?

To be a correctly working and displaying Material Design progressbar.

What is the current behavior?

It's not displayed correctly.

What are the steps to reproduce?

Just open the progressbar from the docs with Firefox.

screenshot

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Angular Material 2.0.0-beta.12
At least Firefox 56

@josephperrott josephperrott self-assigned this Oct 6, 2017
@josephperrott josephperrott added P2 The issue is important to a large percentage of users, with a workaround needs investigation A member of the team needs to do further investigation to determine the root cause labels Oct 6, 2017
@ghost
Copy link
Author

ghost commented Oct 6, 2017

This is a really strange issue. When hover over any element with the inspector, the problem disappears. As soon as I exit inspector mode it reappears.

I'm not sure anymore if this is really an Angular MD issue rather than a Firefox issue.

@josephperrott
Copy link
Member

I am fairly certain its a firefox regression, as nothing changed in the progress-bar code and this issue can be seen occurring a few version back as well.

However, I was not able to reproduce it when I extracted the dom structure and css out and ran it separately. It will definitely require more investigating.

@shalugin
Copy link

shalugin commented Oct 7, 2017

Firefox team changed their css engine recently.

@shalugin
Copy link

shalugin commented Oct 7, 2017

I've triggred a bug in BugZilla - https://bugzilla.mozilla.org/show_bug.cgi?id=1406623

@josephperrott
Copy link
Member

As an update, it looks like the regression will hopefully be addressed in FF 58

@crisbeto crisbeto self-assigned this Dec 25, 2017
crisbeto added a commit to crisbeto/material2 that referenced this issue Dec 25, 2017
Works around an issue in Firefox 57 and above where the animated elements in the progress bar start leaving trails as they animate.

Fixes angular#7606.
jelbourn pushed a commit that referenced this issue Jan 4, 2018
Works around an issue in Firefox 57 and above where the animated elements in the progress bar start leaving trails as they animate.

Fixes #7606.
jelbourn pushed a commit to jelbourn/components that referenced this issue Jan 8, 2018
Works around an issue in Firefox 57 and above where the animated elements in the progress bar start leaving trails as they animate.

Fixes angular#7606.
jelbourn pushed a commit to jelbourn/components that referenced this issue Jan 9, 2018
Works around an issue in Firefox 57 and above where the animated elements in the progress bar start leaving trails as they animate.

Fixes angular#7606.
jelbourn pushed a commit that referenced this issue Jan 9, 2018
Works around an issue in Firefox 57 and above where the animated elements in the progress bar start leaving trails as they animate.

Fixes #7606.
tinayuangao pushed a commit that referenced this issue Jan 10, 2018
Works around an issue in Firefox 57 and above where the animated elements in the progress bar start leaving trails as they animate.

Fixes #7606.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs investigation A member of the team needs to do further investigation to determine the root cause P2 The issue is important to a large percentage of users, with a workaround
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants