Hey there, just to warn you, I'm tired and on the verge of falling over from sleep debt, so I'm not all that coherent and struggling to spell, etc. But: Yes, Firehamster 1.0.something, the l;ines of one of the entries appares stuck between two other entries you described, just like that. I'm glad you described it, because I wouldn't notice it without reading theorouh the hwole page and I'm in no state to do that ATM. Page info thing says it's in "STandards Compliance mode", which is interesting bmecause I thought maybe it might have been in a glitch-fixing mode (Firehamster fixes lots of peoples' unsepakeabley broken HTML as I'm sure you know, which means that it might maybe unfix working HTML perhaps, I'm not sure ATM).
I did have the more helpful idea though, of feeding the page to Dillo, which (in the old version I still have) spews out all the errors that occur in a webpage. Usually reames of the damn things, the way most people code. As the page loaded, I got.... nothing. The page loaded fine. I looked, and there wa nothing peculiar around the areas that had gone wrong, so I checked the source then, and I didn't see anything weird there either. Then I noticed that actually YES it had printed something since I first looked.
HTML warning: line 1236, unexpected closing tag: </body>. -- expected </a>
Now presumabley that means that the actual error isn't at line 1236 but somewhere earleier where you didn't somehow match ancohr tags, or something, but I dunno. Maybe also it might have been all the P tags you closed, I don't know how commonplace that is, maybe it upset something *shrug* Don't ask me, I'm just guessing :D
Anyway, good luck :) I'm off to bed, or soon anyway.
(no subject)
just to warn you, I'm tired and on the verge of falling over from sleep debt, so I'm not all that coherent and struggling to spell, etc. But:
Yes, Firehamster 1.0.something, the l;ines of one of the entries appares stuck between two other entries you described, just like that. I'm glad you described it, because I wouldn't notice it without reading theorouh the hwole page and I'm in no state to do that ATM. Page info thing says it's in "STandards Compliance mode", which is interesting bmecause I thought maybe it might have been in a glitch-fixing mode (Firehamster fixes lots of peoples' unsepakeabley broken HTML as I'm sure you know, which means that it might maybe unfix working HTML perhaps, I'm not sure ATM).
I did have the more helpful idea though, of feeding the page to Dillo, which (in the old version I still have) spews out all the errors that occur in a webpage. Usually reames of the damn things, the way most people code. As the page loaded, I got.... nothing. The page loaded fine. I looked, and there wa nothing peculiar around the areas that had gone wrong, so I checked the source then, and I didn't see anything weird there either. Then I noticed that actually YES it had printed something since I first looked.
Now presumabley that means that the actual error isn't at line 1236 but somewhere earleier where you didn't somehow match ancohr tags, or something, but I dunno. Maybe also it might have been all the P tags you closed, I don't know how commonplace that is, maybe it upset something *shrug* Don't ask me, I'm just guessing :D
Anyway, good luck :) I'm off to bed, or soon anyway.