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

Ghostery findings not showing correctly in Firefox when launched from overflow menu #449

Open
ondrahlavac opened this issue Sep 13, 2019 · 5 comments

Comments

@ondrahlavac
Copy link

@ondrahlavac ondrahlavac commented Sep 13, 2019

Description

In the browser toolbar, when Ghostery icon is moved to the overflow menu in Firefox, the detailed view is broken and won't show due to lack of space.
See attached images.

Correct view:
Image
Ghostery moved to Overflow menu
Image
Ghostery findings window opened from the Overflow menu
Image

Expected Behavior

Ghostery should either have a responsive layout or display outside of the overflow menu container.

Actual Behavior

Ghostery displays its findings dialog inside of the overflow menu container/dialog, thus making half of it unreadable.
See attached images.

Steps to Reproduce

  1. Open customize toolbar in firefox
  2. Move Ghostery icon to the overflow menu
  3. Save the toolbar layout
  4. Open overflow menu (>>)
  5. Click on Ghostery icon

Versions

  • Browser: 70.0b5 64-bit
  • OS: Win10
  • Node: n/a
  • NPM: n/a
@ondrahlavac
Copy link
Author

@ondrahlavac ondrahlavac commented Sep 13, 2019

Same thing happens in FF 69.0 (64-bit)

@ondrahlavac
Copy link
Author

@ondrahlavac ondrahlavac commented Sep 13, 2019

Not a problem for me. Just thought you should know about it. ;-)

@christophertino
Copy link
Member

@christophertino christophertino commented Sep 25, 2019

Thanks for reporting. This has been a known issue for a little while. We have plans to pull out the old Foundation framework and when we do, we'll make the panel view responsive.

@spbuda
Copy link

@spbuda spbuda commented Jan 7, 2020

How can you label this "feature enhancement" when the feature doesn't work in its current state? That seems pretty short sighted to me. I mean, I guess it's maybe technically true, but that's a completely ludicrous labeling.

@SilverSaw
Copy link

@SilverSaw SilverSaw commented Feb 16, 2020

I just want to remind that this is still an issue today !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants