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

Vex strange behaviour on IE9 #61

Closed
Goiking opened this issue Jun 20, 2014 · 8 comments
Closed

Vex strange behaviour on IE9 #61

Goiking opened this issue Jun 20, 2014 · 8 comments

Comments

@Goiking
Copy link

Goiking commented Jun 20, 2014

Hi,
we've used the beatiful vex on our code.

It works perfectly on our site (we even changed the width on some place).

But it appears that standard vex code like this:

//The code On the screen
image

Render the vex strange.

Next Screen is how it appears on IE11:

image

And this on ie9 portable:

image

it appears on the bottom of the page...

I suppose this is a vex problem, here how it appears the vex demo:

image

First i do not see all the vex like on chrome,
second one vex is one another...
Third, it seems to me that only some vex are shown. (4 or 5).

@adamschwartz
Copy link
Contributor

Unfortunately I wasn't able to reproduce this issue in IE9.

Here's a screenshot of the docs login example working (which your code above is loosely based on).

screen shot 2014-06-20 at 12 51 56 pm

If you can isolate and reproduce the bug in jsfiddle.net, that might help. But my guess is you have some conflicting CSS which is causing the dialog to not be positioned. (Perhaps something is setting it to position: static?)

@Goiking
Copy link
Author

Goiking commented Jun 25, 2014

Hi,
i've got, display table, block, table-cell, inline-block, but not static.

Do you want the link? I can give you a link to the site we're working on if
you want to...

2014-06-20 18:54 GMT+02:00 Adam Schwartz notifications@github.com:

Unfortunately I wasn't able to reproduce this issue in IE9.

Here's a screenshot of the docs login example working (which your code
above is loosely based on).

[image: screen shot 2014-06-20 at 12 51 56 pm]
https://cloud.githubusercontent.com/assets/154613/3343113/305f126c-f89b-11e3-90c9-a79be31a1d69.png

If you can isolate and reproduce the bug in jsfiddle.net, that might
help. But my guess is you have some conflicting CSS which is causing the
dialog to not be positioned. (Perhaps something is setting it to position:
static?)


Reply to this email directly or view it on GitHub
#61 (comment).

@adamschwartz
Copy link
Contributor

I was referring to the position property, which has possible values of static, relative, absolute, fixed, and inherit (and sticky, soon).

Yes, if you have one, please share a link to a reproducible bug.

@Goiking
Copy link
Author

Goiking commented Jun 25, 2014

Here the link: http://www.assirevi.it/system/index.php

If you Click in this page on "Area Riservata" you'll call a vex.

On the site there are others vex if you need, they are used on all our site.

2014-06-25 20:12 GMT+02:00 Adam Schwartz notifications@github.com:

I was referring to the position property, which has possible values of
static, relative, absolute, fixed, and inherit (and sticky, soon).

Yes, if you have one, please share a link to a reproducible bug.


Reply to this email directly or view it on GitHub
#61 (comment).

@adamschwartz
Copy link
Contributor

I'm seeing a javascript error preventing the app from fully loading. So for me, clicking "Area Riservata" doesn't do anything.

screen shot 2014-06-25 at 4 13 49 pm

@Goiking
Copy link
Author

Goiking commented Jun 25, 2014

Uploaded the page with the code fixed, sorry about the delay.

2014-06-25 22:14 GMT+02:00 Adam Schwartz notifications@github.com:

I'm seeing a javascript error preventing the app from fully loading. So
for me, clicking "Area Riservata" doesn't do anything.

[image: screen shot 2014-06-25 at 4 13 49 pm]
https://cloud.githubusercontent.com/assets/154613/3390969/2db2f570-fca5-11e3-812f-6e699d914f2a.png


Reply to this email directly or view it on GitHub
#61 (comment).

@adamschwartz
Copy link
Contributor

I believe the issue is your DOCTYPE declaration.

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

Change that to <!DOCTYPE html> and I believe your issue will resolve.

@Goiking
Copy link
Author

Goiking commented Jun 26, 2014

Yes, it was that!

Thanks a lot ^_^

2014-06-26 0:50 GMT+02:00 Adam Schwartz notifications@github.com:

I believe the issue is your DOCTYPE declaration.

Change that to and I believe your issue will resolve.


Reply to this email directly or view it on GitHub
#61 (comment).

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

No branches or pull requests

2 participants