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

Overlay panel arrow displayed on the wrong side in IE #7832

Closed
AlekKj opened this issue Jun 21, 2019 · 1 comment
Closed

Overlay panel arrow displayed on the wrong side in IE #7832

AlekKj opened this issue Jun 21, 2019 · 1 comment
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@AlekKj
Copy link

AlekKj commented Jun 21, 2019

I'm submitting a ... (check one with "x")

[x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Current behavior:

  1. Open the link in Internet Explorer: https://www.primefaces.org/primeng/#/overlaypanel
  2. Click on any search icon you want.
  3. Notice that the arrow has been display on the wrong side.

Expected behavior:
Expect to have the arrow on the correct place, as it behaves on the other browsers (Chrome, Edge...)

What is the motivation / use case for changing the behavior?
Consistency and better looking design! It should behave like it is in the other browsers.

- Angular version: 8.X
- PrimeNG : 7.X
- Browser: Internet Explorer 11
- Language: all

@cagataycivici cagataycivici self-assigned this Jul 23, 2019
@cagataycivici cagataycivici added the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Jul 23, 2019
@cagataycivici cagataycivici added this to the 8.0.2 milestone Jul 23, 2019
@surensubhu
Copy link

@cagataycivici Is it possible to push this change to 7.x.x? As we are still using Angular 7 and no plans to use Angular 8 near soon.

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

4 participants