Skip to content

Loading…

styles not applied until mouseover/mouseout #23

Closed
hbstone opened this Issue · 7 comments

3 participants

@hbstone

At least in IE7 on XP, the styles applied to the top left nav links on http://arguments.callee.info/ don't get applied until I mouse over the element.

I thought it wasn't working at all at first, because I could use other elements on the page and the nav link still had no border radius, but then when I moved the mouse over the element it suddenly got a border radius and shadow.

If I refresh while the mouse is on top of the element, the radius/shadow do not appear until I completely mouse out of the element.

@hbstone

I applied it to another element (search box in the top right) and it seems to work fine without user interaction.

@lojjic
Owner

Thanks for the bug report. I can verify the problem occurs. Not sure why it's happening.

Would you be willing to try putting together a minimal testcase?

@hbstone

I'll give it a shot, sure.

@hbstone

Copied only those two elements and their related CSS to http://arguments.callee.info/sandbox/pie/

It's not completely minimal, there's some CSS I could pull out (colors etc) but should be a lot easier than wading through the live site. Let me know if you do need me to start pulling stuff out of the remaining CSS, I can do that tonight.

@lojjic
Owner

Commit http://github.com/lojjic/PIE/commit/ca4e5b25337c55401952d97272517ea2a5ec7522

I'm still not totally clear why this particular testcase was failing. It seems that in rare cases, the initial script execution happens before the element's readyState is complete, but its oncontentready event doesn't fire. Adding a listener for ondocumentready as a last-ditch effort seems to get around it.

@alanpolhoatzin

Hello, I tried the ondocumentready fix but it does not work for me :( any suggestions??? Thanks!!!

@lojjic
Owner

@alanpolhoatzin: Can you provide a testcase that shows the failure you're seeing?

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.