Several comments I’ve read in the last few hours aren’t word wrapping correctly. Hopefully, if I keep making this sentence as long as possible this would also show up in a Forum post.
Annoying, to say the least.
RoHo
Premium Member<p>Annoying, annoying, annoying. Paul, please fix this!</p>
Brad Sams
Premium Member<p>Do you have a link to an example?</p>
hrlngrv
Premium Member<p><a href="#136297"><em>In reply to brad-sams:</em></a></p><p>From a few minutes ago (22:45 Zulu), Premium comments to https://www.thurrott.com/windows/windows-10/121416/yes-microsoft-promise-timeline-fall-creators-update</p><p><img src="http://imgur.com/q0W0wnK.jpg"></p><p><strong><em>ADDED:</em></strong> only happens in Firefox. Chrome and Opera have correct word wrap on my system.</p>
madthinus
Premium Member<blockquote><a href="#136297"><em>In reply to brad-sams:</em></a></blockquote><p>Hi Brad. </p><p><br></p><p>I see this in Edge and Firefox. You can see it well when you resize the page. </p>
RoHo
Premium Member<p>try to read the comments on this article, word wrap isn't working. I have to re read a sentence all the time.</p><p><br></p><p>https://www.thurrott.com/paul/121346/just-doesnt-work</p>
Brad Sams
Premium Member<p>If you are seeing this bug, please let me know what browser…a screenshot would be helpful too.</p>
RoHo
Premium Member<p>It appears that the word wrap issue is with Firefox. I logged in with Chrome and don't see it. </p><p><br></p><p>Anyone know how to fix word wrap in FF? I'm not giving up FF. I just won't do comments here anymore. </p>
hrlngrv
Premium Member<p><a href="#139419"><em>In reply to RoHo:</em></a></p><p>It also appears in Edge, FWLIW.</p>
jean
<blockquote><a href="#139463"><em>In reply to hrlngrv:</em></a></blockquote><p>Edge is fine (at least on my computers)</p>
Oasis
Premium Member<p>What is the status of this issue</p>
Brad Sams
Premium Member<blockquote><a href="#147623"><em>In reply to Oasis:</em></a></blockquote><p>Will follow-up today, I know a fix was in the works last week.</p>
Brad Sams
Premium Member<blockquote><a href="#147623"><em>In reply to Oasis:</em></a></blockquote><p>We pushed an update last week that fixed what we thought were most/all of the issues…where are you still seeing this?</p>
hrlngrv
Premium Member<p><a href="#149184"><em>In reply to brad-sams:</em></a></p><blockquote>. . . where are you still seeing this?</blockquote><p>This was fixed for a few days. Well, words at ends of lines were hyphenated. However, the bug is back. Following is part of a screen shot from Firefox 54.0.1 (64-bit) under Linux. Same problem using Firefox under Windows. Edge too.</p><p><img src="https://s11.postimg.org/bvx7rgbbn/deleteme.jpg"></p>
Brad Sams
Premium Member<blockquote><a href="#149239"><em>In reply to hrlngrv:</em></a></blockquote><p>ok will pass this along, thanks.</p>
Oasis
Premium Member<blockquote><a href="#149184"><em><img src=""><img src=""><img src="http://s24.postimg.org/vortsif3p/screenshot_8.png">In reply to brad-sams:</em></a></blockquote><p>This was in Firefox 64bit Windows 7…..</p>
RoHo
Premium Member<p>It was still present today when I read your post on cable cutting</p>
hrlngrv
Premium Member<p>Still screwed up as of 19:55 Zulu 23 July 2017. I'd note that it looks like this site is trying to right-align comment text.</p><p><img src="https://s21.postimg.org/xzh8gyglz/deleteme.jpg"></p>
Oasis
Premium Member<p> Still broken for Firefox on Windows(7) after 17 days. What is up with that? </p>
qwerty2002
<p>We have a job to do, please fix it quickly?</p>
Lewk
Premium Member<p>This is also happening in Edge.</p>
Brad Sams
Premium Member<blockquote><a href="#152074"><em>In reply to Lewk:</em></a></blockquote><p>Thanks, devs are aware of the on-going issue.</p>
Oasis
Premium Member<p> 3 weeks and counting. </p>
Tim
Premium Member<blockquote><a href="#154336"><em>In reply to Oasis:</em></a></blockquote><p><br></p><p>So here's the deal…</p><p><br></p><p>This fix was live and for a number of days. This fix was pushed out with a batch of code that contained an issue that impacted a small number of members in a completely unrelated but significantly more detrimental fashion.</p><p><br></p><p>That issue is tied to a conflict with a third party vendor's code. That conflict is being worked on (alongside that 3rd party vendor) right now. It is my hope that both of these known bugs are addressed and live before the end of the weekend. </p><p><br></p><p><br></p>
Oasis
Premium Member<blockquote><a href="#154438"><em>In reply to Tim:</em></a></blockquote><p>Thanks for the clarifications. </p>
Oasis
Premium Member<blockquote><a href="#154438"><em>In reply to Tim:</em></a></blockquote><p>Which weekend were you referring to, this is 8/4/2017 and it still is in the wind.</p>
hrlngrv
Premium Member<p><a href="#164701"><em>In reply to Oasis:</em></a></p><p>If Firefox and Edge users make up less than 10% of the visitors to thurrott.com, it wouldn't be completely unreasonable for this to be a back burner issue. We just ain't a priority, and the BWW people are too polite to be explicit about that.</p>
Oasis
Premium Member<blockquote><a href="#164730"><em>In reply to hrlngrv:</em></a></blockquote><p>I would curious as to what those numbers were.</p>
RoHo
Premium Member<p>So now we're getting spammed in the comment section! This site is seroiusly disappointing. I frequent many forums and none have word wrap issues let alone allow spammers in!</p><p><br></p><p>Suprtra needs to be banned. </p><p><br></p><p>Can I get a refund on my premium membership? </p>
Oasis
Premium Member<p> This thread is becoming a SPAM thread. The Word Wrap is still seriously FUBAR. This may explain why it is taking much longer than anticipated. Hmmm, it seems to be working now ( at least this post) but not on the older entries. So, maybe not…. edit1: nope still hosed… edit2: I see all the spam posts were removed, thank you</p>
Oasis
Premium Member<p> Four Weeks now and no resolution to this issue. Well, at least the spam comments have ceased.</p>
hrlngrv
Premium Member<p><a href="#163414"><em>In reply to Oasis:</em></a></p><p>Have you used any other browser-based comments system which has had this problem in any browser? I haven't, but I may not use many comment systems.</p>
Oasis
Premium Member<blockquote><a href="#163479"><em>In reply to hrlngrv:</em></a></blockquote><p>I use Disqus and It doesn't act up like this…</p>
hrlngrv
Premium Member<p>At the moment, 20:45 Zulu 4 August 2017, it looks like it's fixed again.</p><p><img src="https://s2.postimg.org/ji7qt6el5/deleteme.jpg"></p><p>Odd that Firefox apparently needs to handle this via hyphenation rather than crude word wrap, which would have put <strong><em>interesting</em></strong> all on the 3rd line and shifted subsequent text down, which is what Chrome and Opera do. I don't use any other commenting system which needs hyphenation rather than crude word wrap for Firefox.</p>
Oasis
Premium Member<blockquote><a href="#164813"><em>In reply to hrlngrv:</em></a></blockquote><p>Fixed my A$$, This is just Duct Tape. It didn't need hyphenation to work. This is probably just what they had to do because they couldn't figure it out. That 3rd party program they mentioned probably isn't play nice with their efforts and so we got the Disneyland solution. Lipstick on a PIG.</p>
hrlngrv
Premium Member<p><a href="#164854"><em>In reply to Oasis:</em></a></p><p><em>Fixed</em> in the sense that hyphenation is a generally acceptable way to trim long lines of text. Certainly better than breaking words at any character. Agreed it's not the best way to fix this, and to repeat it seems odd that Firefox can't wrap the same way that Chrome and Opera can.</p>
Oasis
Premium Member<blockquote><a href="#164857"><em>In reply to hrlngrv:</em></a></blockquote><p>I noticed it is like that(hyphenated) in the Neowin comment too.</p>
Oasis
Premium Member<blockquote><a href="#164857"><em>In reply to hrlngrv:</em></a></blockquote><p>I tried the comments on KrebsOnSecurity.com and those wrap normal and don't use any Hyphens, so it isn't a Firefox issue by itself. It used to work here just fine.</p>
hrlngrv
Premium Member<p><a href="#164913"><em>In reply to Oasis:</em></a></p><p>It started going bad when notifications went live.</p><p>Mere coincidence? Not likely.</p>
Sign up for our new free newsletter to get three time-saving tips each Friday
"*" indicates required fields