News for hackers. Stuff that matters.
Re:Chrome phasing out support for User-Agent by mmis1000 on Wednesday March 25, 2020 @01:00PM (#22686429)
It actually insert a line break on enter, make it invisible and can't be deleted only on firefox.

Pretend firefox as chrome makes it works perfectly.

They lock the community thread and fixed that after several days I found the finding and post it there.

Shame on you, google.

Re:Chrome phasing out support for User-Agent by llbeansandrice on Wednesday March 25, 2020 @01:47PM (#22686834)
Oh my god. I knew it was inserting a line break when I hit enter but I didn't realize it was a FF only issue. gdi Google.
Re:Chrome phasing out support for User-Agent by _jal on Wednesday March 25, 2020 @02:32PM (#22687167)
Not the first time. For some reason Google really doesn't like people talking about the games they play with browser detection.

(That's not snark - I really don't get it. They don't appear to mind people talking negatively about a lot of other stuff they get up to. Maybe lingering antitrust fears from the 90's MS suit?)

Re:Chrome phasing out support for User-Agent by ksec on Wednesday March 25, 2020 @07:08PM (#22689286)
I mean we are in 2020, none of this should be news, but then a lot of people only discovered them now. They have been doing this since early 2010s.

They have been a hypocrite from the start, but people got too consumed with its free Gmail, RSS Reader along with its Do no Evil they decided to trust them blindly.

The current browser, and Web Tech scenario is pretty much Google's way or the highway. So I am glad Apple kept Safari as the only option on Apple platform. Not allowing them to dictate everything.

Re:Chrome phasing out support for User-Agent by cpeterso on Thursday March 26, 2020 @01:14AM (#22690896)
I reported this as a Firefox bug [1] in 2015. Google fixed it on their side in 2017, but it’s back. :(

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1205573

Re:Chrome phasing out support for User-Agent by philwelch on Wednesday March 25, 2020 @03:07PM (#22687477)
Companies are afraid of legal liability much more than they’re afraid of bad PR.
Re:Chrome phasing out support for User-Agent by NotSammyHagar on Wednesday March 25, 2020 @03:07PM (#22687475)
I was hitting that too! I wondered what I was doing. I kept getting these weird fields. That fucking sucks. I'd like someone to explain google's point of view about why this is happening? I do override user agent on some systems so random websites work.
Re:Chrome phasing out support for User-Agent by cozzyd on Wednesday March 25, 2020 @03:14PM (#22687568)
Indeed, I was wondering why sheets was so broken to always randomly insert line returns.
Re:Chrome phasing out support for User-Agent by lmpostor on Wednesday March 25, 2020 @02:23PM (#22687097)
Same... I've been played.
Re:Chrome phasing out support for User-Agent by nannal on Wednesday March 25, 2020 @02:16PM (#22687051)
really working hard to shove that poison apple down your throat.
Re:Chrome phasing out support for User-Agent by true_religion on Thursday March 26, 2020 @06:08AM (#22692073)
I wouldn’t really shame them on this one. Google docs and sheets uses contenteditable under the hood. Contenteditable isn’t specified or standardized anywhere and varies wildly between browsers, and sometimes between browser versions.
Re:Chrome phasing out support for User-Agent by r00fus on Wednesday March 25, 2020 @07:51PM (#22689587)
So even that workaround is being phased out with this UA support change?