Subtle changes, bugs and feedback

Posted on
Page
of 312
  • On this version of Firefox (24.7.0, on Debian) word-wrap isn't working for posts. Words are split where they meet the end of the line. This is quite new - wasn't doing it a few days ago. Couldn't say when precisely it started.

  • And now it's working again. Hmm. Quite possibly my browser (or a plug-in) temporarily misbehaving.

  • It started moments ago.

    We are looking into it.

    We actually pushed that change believing it might break but not knowing where. We ran browserscreenshots and browserstack first and witnessed it working almost everywhere, but then breaking in odd places but inconclusively and not in a repeatable way.

    We hoped, thankfully correctly, that we would be told if it broke and what for.

    Firefox 24 on Linux... cool, thank you.

  • I had suspected Vimperator to be the guilty plug-in. There's always a risk, with that, of accidentally hitting a key sequence/combo which changes a Firefox setting. Oh, and it's broken again. Oddly, when it is broken, it sometimes affects post-editing (so that word wrap doesn't happen while typing) and sometimes does not.

  • Reverted.

    CSS control of width of line when you have impossibly long strings is just not there yet.

    Hello <wbr> my old friend.

  • Reverted.

    I was just about to tell you it was broken on FF 31 , Windows 7 but I did a refresh and it was fixed . .


    1 Attachment

    • microc.png
  • I couldn't find an example of anyone searching by author in the old vBulletin database

    It's quicker than finding wherever I posted it last.

    Hmm. I used to search by author on vBulletin in order to find all the times I've answered the same question when a particularly egregious failure to #UTFS occurred :-)

  • alksjdlakjsdlakjsdlkajsdlkajsdlkjasdlkajsdlkajsdlkjasdlkjalskdjalksjdlkajfskshfoiwjeoiuweorjlksfhjlkajnfmnsmdnfbsjkdfsdfhdjflksjdflkjsldkfjslkjdflksjdflksjdlfkjsldkfjslkdjflksjdflksjdflkjsldkfjslkdfjlksjdflksjdflksjdflkjsdlkfjsldkjfslkdjflskjdflksjdflksjdflksjdflkjsdlkjsdlkfjsldkfjsldkfjslkdfjlskdfjlskdfj

  • ^that sort of thing makes two finger scrolling a nightmare

  • Nb, I don't think my old forum subscriptions were working, went in unticked and reticked and now they are...

    Specifically the LPC and lhbpa forums that were subsections of polo before. Not sure if them being closed forums has something to do with it.

    Also would be nice if the forum numbers were in some way similar to the old ones... Polo being 024 or something would make it easy enough for a lot of polo players... (Would also be able to remember 042, 036 and 048, I think)

  • those numbers......reminds me of old people that say "have a look on double-u double-u double-u dot Google dot com" instead of saying "Google it."

  • @Velocio

    In this post the image is displayed rotated 90 degrees left in Chrome on my laptop, but correctly in Safari on iOS7/iPhone. Is it my laptop, or is something amiss?

  • @apollo, you'd have learnt them too if you had been on the old forum long enough ;-p

    Radar, vb explained it already, possibly in one of the Miriad of other bug threads, basically the picture comes from a phone or camera that records the image and then puts a tag in to say that it was taken sideways, your phone is reading the tag (so realigning the photo) your lap top is ignoring the tag.

  • Cheers, that makes sense.

  • Deeper explanation: http://www.daveperrett.com/articles/2012/07/28/exif-orientation-handling-is-a-ghetto/

    The safest thing for people to do, is to correct their images using an editing programme before uploading to the web.

  • Really annoyingly if you view the image directly Chrome orientates it the right way: https://lfgss.microcosm.app/api/v1/files/b697c837bfa6bd0accb4329b5e7af5b184040bbe.jpg

  • Should I ever be seeing these?

  • @Velocio Are you running Django in debug mode true?
    Went on the forum only see a long list of debug info from Django

    Got it in PDF if you want to have a look

  • Ah!!!

  • Can't view the .mht files.

    And Django should not be running in debug, and I've just pushed the prod version again with it disabled and re-verified that it is disabled.

  • Cool. Still if you need the PDF, it's on my tablet (where I experienced the issue)

  • Can't view the .mht files.

    Wouldn't help if you could, the saved file isn't the one which was displayed on my screen as the browser fetched them afresh and by then the errors had vanished.

    They were Django debug pages

  • Ah! I got the proper stuff in the PDF :-p #teachesbeingbitchaboutbeingfirst

  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview
About

Subtle changes, bugs and feedback

Posted by Avatar for Velocio @Velocio

Actions