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

Waypoints box fighting with Layer Selector popup #3

Open
waynegraham opened this issue Aug 25, 2014 · 4 comments
Open

Waypoints box fighting with Layer Selector popup #3

waynegraham opened this issue Aug 25, 2014 · 4 comments

Comments

@waynegraham
Copy link

From jenbartle performant-software/Neatline#327

Hi--
When using the Waypoints widget, the Layer Selector popup box works as expected the first time only. After that, it is pushed behind the the Waypoints box and cannot be used again (it will open and close, but you cannot select a different layer a second time because the popup is pushed behind the Waypoints box.
[Omeka v.2.2.2; Neatline v.2.3.0; Neatline Waypoints v.2.0.2.]
Thanks!
Jen

@waynegraham
Copy link
Author

@jenbartle Which browser are you using (just to set up failing test case)?

@jenbartle
Copy link

It happens in both FFox and Chrome.

@davidmcclure
Copy link
Contributor

Hey @jenbartle - What version of Neatline? We made a change to the layer switcher in 2.3 that fixed a problem that would cause the widget to get hidden below the waypoints container when a Google layer was activated (long story). It sounds like you might be hitting something else, though I can't replicate it. Is there a live link to the exhibit?

@davidmcclure
Copy link
Contributor

I just looked into this, and it turns out to be a rather tricky problem. It happens when a Google layer is activated, which changes the markup structure of the map and create a new z-index stacking context. I actually found a way to clobber some styles in the Google API in a way that fixes this problem, but not without messing up lots of other stuff (the Google tiles start to slide over and occlude other elements on the page, etc).

@waynegraham, this, I guess, is the sort of thing that made the OL developers want to abandon Google entirely, and I suppose can't really blame them. Probably best to shelve this problem until we do the OL3 or Leaflet migration, which will likely fix this automatically.

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

No branches or pull requests

4 participants