Closed Bug 332951 Opened 18 years ago Closed 18 years ago

Pages borking. New pages starting inside divs.

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: cameron, Assigned: clouserw)

References

()

Details

Attachments

(4 files)

 
Severity: minor → major
Refreshed & hard refreshed many times to no avail. Closed browser, restarted and all appears fine. -> WORKSFORME

If anyone else sees this, please let me know. Might be caused by something erroring somewhere that doesn't happen every time
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Unable to reproduce the chatzilla problem, but 3 people able to reproduce a slightly different (but I suspect related) problem on the Midnightfox page.
Status: RESOLVED → VERIFIED
Summary: Chatzilla page borked. New page starts inside maincontent div → Pages borking. New pages starting inside divs.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Screenshot of https://addons.mozilla.org/firefox/2311/
Comment on attachment 217389 [details]
Source code of /firefox/16/

oops, those source codes need to be as text/plain
Attachment #217389 - Attachment description: Source code of page → Source code of chatzilla page
Attachment #217389 - Attachment mime type: text/html → text/plain
Attachment #217388 - Attachment description: Screenshot of problem → Screenshot of /firefox/16/
Attachment #217389 - Attachment description: Source code of chatzilla page → Source code of /firefox/16/
Attachment #217394 - Attachment description: Screenshot 2 → Screenshot of /firefox/2311/
Attachment #217395 - Attachment mime type: text/html → text/plain
That's interesting code Cameron, but I'm not sure why it would do that.  I haven't been able to reproduce it.  Maybe it had something to do with the server issues, when things weren't syncing right and the cache was flaky?

Either way, I'll take it, but if no one sees it anymore, I'll plan on marking it WORKSFORME. Thoughts?
Status: REOPENED → ASSIGNED
I meant to assign that to me, not morgamic :)
Assignee: morgamic → clouserw
Status: ASSIGNED → NEW
Yeah I'm pretty sure it was because of server issues too.. but we should make it so that if the servers screw up somehow, the site gives some neat form of error message, rather than completely borking.

Is that possible/reasonable with current architecture?
If I could duplicate the problem, we could look into it, but so far I've had no luck.
Status: NEW → RESOLVED
Closed: 18 years ago18 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
Target Milestone: 2.1 → ---
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: