Ever heard of this FireFox bug? 4

[Sleidia]

Hi guys,

It's the second time this bug occures and on two different sites of mine.

The problem is that the site looks fine on my local server (localhost) but some areas of the layout get broken once it's online. The local files and the remote files are exactly the same. No doubt about that. Plus, it occures only on FireFox. IE, Opera and Safari are fine.

What could it be?
I suppose that it's a bug thas has something to do with the delay it takes for the page to load (which is way shorter on local computer).
What do you think?

Thanks

 

[Vragabond]

So, you're asking us if we've heard of a bug that only you know what it does and to which elements? Because then I would have to say no. But if you tell us which element the bug appears on, what did you expect to see and what it is you're seeing, provide the CSS, JS and HTML for that element, we might have a better shot at explaining it.

___________________________________________________________
[small]Do something about world cancer today: Comprehensive cancer control information at PACT[/small]

 

[BillyRayPreachersSon]

As Vragabond has mentioned, without seeing any source or knowing anything, we've little to no chance of being able to help.

The only things I can suggest are checking that:

- Your markup validates correctly against your full and complete DOCTYPE.

- You have no backslashes in filenames for HTML/CSS/JS/images includes (so make sure all "\" are "/")

- The case of all your HTML/CSS/JS/image filenames is as per the item (e.g. "Wibble.gif" and "wibble.gif" would be different on some 'nix hosts)

Dan



Coedit Limited - Delivering standards compliant, accessible web solutions

[tt]Dan's Page [blue]@[/blue] Code Couch

http://www.codecouch.com/dan/

[/tt]

 

[Sleidia]

So, you're asking us if we've heard of a bug that only you know what it does and to which elements?

Vragabond, I think you should reread the original post with a less critical mindset

What I'm obviously asking is if there is a well known FireFox bug that occures only when the site is online ( when the page takes longer to load ).

 

[johnwm]

... and we still don't know what the perceived or imagined problem is! No code, no link, no symptoms. On that basis, and knowing that FF is in daily use by millions of users it seems much more likely that your code is the problem.

My guess is that it is a problem on line 23 of your code.

___________________________________________________________
If you want the best response to a question, please check out FAQ222-2244 first.
'If we're supposed to work in Hex, why have we only got A fingers?'
Drive a Steam Roller
Steam Engine Prints

 

[Sleidia]

Actually, beside my personal problem with my code, the most interesting question for me is : why and how a bug would occure only online?

 

[Vragabond]

Again, is this a scavenger hunt for us? Why can't you tell us what is this "bug" you're seeing and are you expecting to be seeing. There are many differences between local and remote versions, but why would I go into lengthy explanations of why your images are broken in FF when viewing your page remotely, if you will only reply with "My images are not broken." If you're unwilling to share the actual problem with us, I suggest two ways of dealing with it:

1. Explore

https://bugzilla.mozilla.org/

and hope to find something similar to what you're experiencing.
2. Try searching Google for [google]well known firefox bug[/tt] and see if there is one.


___________________________________________________________
[small]Do something about world cancer today: Comprehensive cancer control information at PACT[/small]

 

[Sleidia]

Jeez I'm not asking you all to fix my problem ( which took multiple forms and which is used on very complex layouts anyway ).

I'm just asking if someone has heard of a FireFox bug that occures only online. That's it.

So, if you've never heard of this, just relax and don't sweat on it ... it's not as if the world would come to an end you know

 

[ca8msm]

I'm just asking if someone has heard of a FireFox bug that occures only online. That's it.

Nope. I haven't. But then again, how does your browser know whether it is "online" or not. All it does is render some HTML that it is given so whether this comes from a file on your pc or a remote web-server it is irrelevant.

There's no way anyone can answer this question successfully without more information. It's like going to a car garage and saying to the mechanic if he's ever heard on a problem that happens only when a car is being driven. They have probably heard of many problems but would you really expect them to be able to give you a decent answer?




-------------------------------------------------------

Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]

 

[Sleidia]

But then again, how does your browser know whether it is "online" or not.

As I said, one possibility is that the parser acts differently depending on the delay needed for the page to load.

It's like going to a car garage and saying to the mechanic if he's ever heard on a problem that happens only when a car is being driven.

OK, but I thought that this offline/online bug is odd enough to be remembered by anyone who stumbled on it.

Anyway, I don't think it's caused by my code because, again, IE Opera and Safari don't have the problem.

 

[ca8msm]

As I said, one possibility is that the parser acts differently depending on the delay needed for the page to load.

I would have thought that would be highly unlikely.

OK, but I thought that this offline/online bug is odd enough to be remembered by anyone who stumbled on it.

I don't think there is such a thing as being "online" (in terms od rendering HTML), so I certainly wouldn't be able to recall anything like that.

Anyway, I don't think it's caused by my code because, again, IE Opera and Safari don't have the problem.

That doesn't rule out the possibility of it being your code. If you provide a link to the page or the HTML/CSS as everyone is asking then we can tell you for certain whether this is the case or not.





-------------------------------------------------------

Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]

 

[Sleidia]

Sorry, I can't post the URL of the page for some reason.

Anyway, the other funny thing about this bug is that, not only it occures solely on the online site, but it also occures only at the first display of the page. Reloading the page makes it diappear. And, on top of that, the bug never occures on the same place in the page. There are 8 floating divs in the page, and everytime the bug occures, it's on one or several of those divs but never the same ones twice.

Trying different doctypes didn't help either.

 

[Sleidia]

OK, I've finally identified the source of the problem

Inside a <a></a> element set to "display: block", having divs will provoke the problem I've described above. Replacing those divs by spans set to "display: block" fixed the problem.

Dadaaaa!

 

[Vragabond]

I could've told you that 12 hours ago if I'd seen your code.

___________________________________________________________
[small]Do something about world cancer today: Comprehensive cancer control information at PACT[/small]

 

[BillyRayPreachersSon]

Ah well - looks like I was wrong with all of my advice, but hey - them's the breaks ;-)

Dan



Coedit Limited - Delivering standards compliant, accessible web solutions

[tt]Dan's Page [blue]@[/blue] Code Couch

http://www.codecouch.com/dan/

[/tt]

 

[Foamcow]

You shouldn't have a <div> inside an <a> element. You "can't" put block level elements within inline elements, even if you change their display property via CSS.

--
Tek-Tips Forums is Member Supported. Click Here to donate

<honk>*:O)</honk>

Tyres: Mine's a pint of the black stuff.
Mike: You can't drink a pint of Bovril.

 

[Sleidia]

Well, the fact is: spans set to "display: block" work on all the browsers I have on my machine. So, "can't" isn't exactly the proper word I guess

Still, it would be interesting to find out the reason why the bug could be seen only on the online site and always on different places in the page.

Someone wants to throw a theory?

 

[BillyRayPreachersSon]

It could be one of your plugins. Try disabling them all and see if the problem still exists...




Coedit Limited - Delivering standards compliant, accessible web solutions

[tt]Dan's Page [blue]@[/blue] Code Couch

http://www.codecouch.com/dan/

[/tt]

 

[kaht]

So, "can't" isn't exactly the proper word I guess

I guess it all depends on if you care about whether your code validates or not. If you don't mind having non-standard code that won't validate, by all means stick <div> inside <a> or <span> all you'd like. Might as well get rid of your doctype and used table based layouts while you're at it.

-kaht

Lisa, if you don't like your job you don't strike. You just go in every day and do it really half-assed. That's the American way. - Homer Simpson

[small]<P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <B> <P> <.</B>[/small]

 

[Sleidia]

By "standard code that validate", you mean ugly sites that clients don't want, right?

Just for fun, I've submitted the most popular sites that I have in my bookmarks to

http://validator.w3.org.

Of course, none validated.