Welcome to the Lounge

Johnny J.9-Nov-15 3:53

9-Nov-15 3:53

Here you go. And HERE[^] is a dump of what it looks like... Smile | :)

User Agent Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
CRC 66365947
Edge False
Gecko True
IE False
Opera False
Safari False
Blink False
WebKit False
Browser Firefox
Platform Type Desktop
Standard True
Display Mode Normal
Version string 0.0
Version 0
Platform Win8.1
Platform Version 6.3
Editable Elements False
Mobile Device False
Small Mobile Device False
Touch Device False
Desktop True
Tablet False
Modern False
Semi-Modern False
Cookies OK? True

Server Web03
Country Sweden
Location Unknown, Sweden
Client IP address: 82.99.4.155 (compact form: 1382220955)

Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
I'd just like a chance to prove that money can't make me happy.
Me, all the time

Chris Maunder9-Nov-15 4:05

9-Nov-15 4:05

The short answer is: bad data our end

The long answer is: we sometimes render based on browser. Very old (or mobile browsers) can't handle the functionality of desktop browsers, so simply don't emit certain HTML for them. We could (and should) use a responsive design whereby features are activated vua client-side script, but many moons ago we made the decision to support non-Javascript browsers, and also to be kind to those on low bandwidth.

For the most part we're now sending down everything and rendering what the client can handle, but for some things such as the edit page we're rendering at server side based on client browser.

The issue for us is that the browser definitions we're using, while only a few days old, are still out of date. I'm in the process of switching to a far more robust system.

This hasn't happened in ages. and I'm wondering if it's a sign of Firefox either revving too often or just not being on people's radars (at least the ones maintaining the useragent list we use)

cheers
Chris Maunder

Johnny J.9-Nov-15 4:12

9-Nov-15 4:12

But the strange thing is that I haven't switched browser or done ANYTHING that can affect this, and it has worked pefectly up until today?!?!

chriselst9-Nov-15 4:19

chriselst

9-Nov-15 4:19

I started getting it end of last week (I think), using Firefox.

Think I remember Firefox asking to restart because of an update at some point too, may or may not have been the start of it.

Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.

Jeremy Falcon9-Nov-15 4:33

Jeremy Falcon

9-Nov-15 4:33

If FF was updated, but their browser definitions file wasn't then it can get a bit out of sync.

Jeremy Falcon

Jeremy Falcon9-Nov-15 4:31

Jeremy Falcon

9-Nov-15 4:31

HTML

<!doctype html>
<html lang="en-us">
<head>
    <noscript>You're on Lynx or you have issues. Go away. We don't want non-JavaScript folk around here.</noscript>
</head>
<body>
</body>
</html>

I've started using something along these lines when doing script-based SPAs. I figure this day and age, if they don't have scripts running they deserve what they get.

Jeremy Falcon

Chris Maunder9-Nov-15 4:35

9-Nov-15 4:35

Subtle and understated. I like it.

cheers
Chris Maunder

Johnny J.9-Nov-15 4:36

9-Nov-15 4:36

LOL - hope your employer agrees once he's had a customer on the phone complaining about rude messages... Poke tongue | ;-P

Dan Neely9-Nov-15 4:54

Dan Neely

9-Nov-15 4:54

Is your system just choking because it doesn't know about Firefox V42 yet; or did Mozilla change something more substantive in the user agent string for the newest release?

Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius

Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt

Chris Maunder9-Nov-15 4:56

9-Nov-15 4:56

Actually that's the interesting thing: I'm still trying to work that out. It turns out we do have entries for FF42 on Win8.1 / WOW64, but the parser just isn't admitting it.

Applying several hammers.

cheers
Chris Maunder

Dan Neely9-Nov-15 5:01

Dan Neely

9-Nov-15 5:01

Ouch. Sounds like the parser is made of many elephants, tightly clustered together. D'Oh! | :doh:

Chris Maunder9-Nov-15 5:02

9-Nov-15 5:02

I'll have to think about that one.

cheers
Chris Maunder

Chris Maunder9-Nov-15 5:37

9-Nov-15 5:37

How is it now?

cheers
Chris Maunder

Jochen Arndt9-Nov-15 6:08

Jochen Arndt

9-Nov-15 6:08

Still not OK (here and in Q&A): No format options and a link to the emoticons.

It was OK at work where the latest Firefox update has not been installed yet. So it should be definitely FF42 related.

Chris Maunder9-Nov-15 9:46

9-Nov-15 9:46

OK, how about now? (Grabbed a larger hammer)

cheers
Chris Maunder

Jochen Arndt9-Nov-15 10:27

Jochen Arndt

9-Nov-15 10:27

Sorry, still not OK.

If it helps:
FF42 with NoScript on Win 7 Pro 64. But all CP relevant URLs are allowed by NoScript.
However, there might be FF profile settings that are not standard (it is an old profile).

Chris Maunder9-Nov-15 13:06

9-Nov-15 13:06

Whats the Useragent string of your browser?

cheers
Chris Maunder

Jochen Arndt9-Nov-15 20:55

Jochen Arndt

9-Nov-15 20:55

The FF here at work has now been updated too and shows the same behaviour. The user agent string is (from the log of the local web server):

"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0"

What I have tried so far without success:

Disabling all extensions (NoScript is the only one)
Clearing the cache
Deleting all Cookies

modified 10-Nov-15 3:37am.

Johnny J.9-Nov-15 20:42

Failure configuring Windows updates.

9-Nov-15 20:42

Back to normal! Big Grin | :-D

Eddy Vluggen9-Nov-15 1:57

Eddy Vluggen

9-Nov-15 1:57

So, it reverted the changes, and is now 'preparing to retry'. The suggested solution comes with weird instructions.

4. lick Repair your computer.

(Source[^])

Bastard Programmer from Hell Suspicious | :suss:

If you can't read my code, try converting it here[^]

W∴ Balboos, GHB9-Nov-15 2:12

W∴ Balboos, GHB

9-Nov-15 2:12

I've seen that myself, and more than once. I've also had Windows updates telling me not to turn my computer off whilst it sits on '15 of 38' or something like that for hours.

Pretty much I end up resetting through it - sometimes twice - until the damn thing is happy. Interestingly, these abort/restart types don't induce problems in later updates, at least not in and obvious pattern.

Fortunately, I didn't look up Micrsoft's idea of help since they're the ones who broke it to begin with. So I didn't see what you really did see, which is an instruction to, basically, lick a box.

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

"As far as we know, our computer has never had an undetected error." - Weisert

"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010

Member 116832519-Nov-15 2:14

Member 11683251

9-Nov-15 2:14

There is a reason why you say to lick your wounds. Wasn't aware it was common when fixing computers. I'm a bit curious as to where they want you to lick the computer. Dead | X|

ZurdoDev9-Nov-15 2:15

ZurdoDev

9-Nov-15 2:15

Eddy Vluggen wrote:
lick Repair your computer.

What's weird about that? I used to use a finger print scanner to logon to my computer but I changed that out for a tongue scanner so now I just lick my way on to the computer. It comes in different flavors too.

There are only 10 types of people in the world, those who understand binary and those who don't.