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

Styles are broken in Microsoft Edge #15120

Closed
vdiaz1130 opened this issue Mar 20, 2024 · 1 comment
Closed

Styles are broken in Microsoft Edge #15120

vdiaz1130 opened this issue Mar 20, 2024 · 1 comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working

Comments

@vdiaz1130
Copy link

Describe the bug

Styles do not render properly in the Edge browser. They look correct in Chrome (Canary as well), Safari, and Firefox.

image

Environment

package.json

    "@angular/animations": "^17.0.0",
    "@angular/common": "^17.0.0",
    "@angular/compiler": "^17.0.0",
    "@angular/core": "^17.0.0",
    "@angular/forms": "^17.0.0",
    "@angular/platform-browser": "^17.0.0",
    "@angular/platform-browser-dynamic": "^17.0.0",
    "@angular/router": "^17.0.0",
    "primeicons": "^6.0.1",
    "primeng": "^17.2.0",
    "rxjs": "~7.8.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.14.2"

node -v 20.7.0
npm -v 10.1.0
OsX 14.2

Reproducer

No response

Angular version

17.0.0

PrimeNG version

17.2.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.7.0

Browser(s)

No response

Steps to reproduce the behavior

git clone [email protected]:thecodedeck/angular-cc-1-client.git
git clone [email protected]:thecodedeck/angular-cc-1-server.git

cd into each and run npm i
Start terminal in each
On client run ng serve
On server run npm start

Check it in chrome.
Check it in MS Edge

Expected behavior

Should render correctly in MS Edge

@vdiaz1130 vdiaz1130 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Mar 20, 2024
@mehmetcetin01140 mehmetcetin01140 added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels May 20, 2024
@mehmetcetin01140 mehmetcetin01140 added this to the 17.17.2 milestone May 20, 2024
@cetincakiroglu cetincakiroglu modified the milestones: 17.17.2, 17.18.0, 18.Future May 29, 2024
@mehmetcetin01140
Copy link
Contributor

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

@github-project-automation github-project-automation bot moved this to Done in PrimeNG Dec 16, 2024
@mehmetcetin01140 mehmetcetin01140 removed this from the 19.x milestone Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

3 participants