+9Key Posted August 9, 2010 Share Posted August 9, 2010 Check out the last few logs on my cache here. They scroll several screens wide. I'm on XP and have looked at the page in both FireFox 3.5 and IE 7 - same scrolling. Any ideas? Link to comment
+Bear and Ragged Posted August 9, 2010 Share Posted August 9, 2010 Well, that's it. You've well and truly broken the site... Link to comment
+Matthew 7:7 Too Posted August 9, 2010 Share Posted August 9, 2010 I can't explain why its happening, but I can confirm that I'm not seeing the logs wrapping either when using Firefox 3.6.8. Chris Link to comment
7rxc Posted August 9, 2010 Share Posted August 9, 2010 I haven't yet seen the log wrap problem... but... I have noticed recently that when I use 'through profile' email to a user, that sometimes when it comes back as a quoted portion of the message, the wrap is definitely lacking... Not in the copy I receive, not in the actual reply text... just the quoted part and not all the time. What I see during creation and in my copy is fine... I hope the recipient sees it fine... haven't had any comments on that in the replies. Only seems to happen during the profile message send. Other email and forum notes seem fine. Last time I saw something like this it was simply a conflict over just what was an end of line marker... and the size of a line. But that was a long time ago... Doug 7rxc. Link to comment
7rxc Posted August 9, 2010 Share Posted August 9, 2010 (edited) Check out the last few logs on my cache here. They scroll several screens wide. Any ideas? A new perk for PM's... extra long log lines! I can't get to them to see them sadly... some day. Doug 7rxc Edited August 9, 2010 by 7rxc Link to comment
+Isonzo Karst Posted August 9, 2010 Share Posted August 9, 2010 When viewed on their own page, they wrap until you get to chachatiff found [Multi-cache] 4000 / 750 Wow... I don't even know where to start... Like Casting Crowns mentioned in his log, we got a VERY early start yesterday that one doesn't wrap even when viewed on it's own page I see nothing in that log that would seem to be the culprit. I even copied it and put it on an unpublished cache of mine, where it wraps okay. Link to comment
+humboldt flier Posted August 9, 2010 Share Posted August 9, 2010 Same problem noted on some of the logs for the ET Trail ie ET 001 Link to comment
OpinioNate Posted August 9, 2010 Share Posted August 9, 2010 When I edited the log Isonzo linked there were no line breaks to be seen. I copied the text and pasted in notepad: still no line breaks. I tried in Firefox and Chrome with the same results. Very curious. I'm certain that log is to blame (along with one on this cache but I won't waste time finding which one). I will write it up, but since we will probably move to the new WYSIWYG editor currently on the trackables pages soon I don't think we'll worry about fixing the bug. Link to comment
+9Key Posted August 9, 2010 Author Share Posted August 9, 2010 Even the log notification emails I got for those logs didn't wrap in my web-based mail or in Outlook. Weirdness! Link to comment
+Lil Devil Posted August 10, 2010 Share Posted August 10, 2010 (edited) I just looked at the source and the issue is in chachatiff's logs. Instead of using space characters between words, he used & nbsp (non-breaking spaces). Seems like something intentional. Edited August 10, 2010 by Lil Devil Link to comment
+Isonzo Karst Posted August 10, 2010 Share Posted August 10, 2010 he used & nbsp mm, I don't see that - within the log panels, I see a single at the beginning of 9Key's log, remarking the "no wrap". - ie, by the time that was on the page, the "no wrap" was already happening. I turned Greasemonkey off. Firefox 3.57 on Windows 2000 Link to comment
+Lil Devil Posted August 10, 2010 Share Posted August 10, 2010 Well, to be more specific, yesterday I used Firebug to view the source. It clearly shows "nbsp" between all the words in chachatiff's logs. Just now I looked at the source in UltraEdit, which is like Notepad on steroids. At first glace, it looks like normal spaces in chachatiff's logs, but when I turn on the HEX viewer feature of UltraEdit, it shows the spaces are ASCII xAO instead of the normal x20. Link to comment
+Isonzo Karst Posted August 10, 2010 Share Posted August 10, 2010 might this be a function of the logs being written in some text editor? picking up some formatting there and then, the user copies and pastes it? I would suspect that particularly here, because the log owner anticipated going over the character limit, so composed the log in something where they could keep count. Just guessing. Link to comment
OpinioNate Posted August 10, 2010 Share Posted August 10, 2010 might this be a function of the logs being written in some text editor? picking up some formatting there and then, the user copies and pastes it? I would suspect that particularly here, because the log owner anticipated going over the character limit, so composed the log in something where they could keep count. Just guessing. I thought that too, but after pasting to Notepad I was under the impression that those formatting eccentricities were stripped out. That didn't happen in this case. Link to comment
+Avernar Posted August 10, 2010 Share Posted August 10, 2010 Well, to be more specific, yesterday I used Firebug to view the source. It clearly shows "nbsp" between all the words in chachatiff's logs. Noticed this a while ago. I thought I mentioned it in one of the release notes threads but can't remember. Just now I looked at the source in UltraEdit, which is like Notepad on steroids. At first glace, it looks like normal spaces in chachatiff's logs, but when I turn on the HEX viewer feature of UltraEdit, it shows the spaces are ASCII xAO instead of the normal x20. 0xa0 is a non breaking space according to this Wikipedia article. Link to comment
+Avernar Posted August 10, 2010 Share Posted August 10, 2010 I thought that too, but after pasting to Notepad I was under the impression that those formatting eccentricities were stripped out. That didn't happen in this case. Looks like it snuck because it's a valid character and not an html escape sequence. Link to comment
Recommended Posts