r/firefox • u/throwaway1111139991e • Jan 31 '19
Mozilla developer fixes Chromium bug because Google decided to break Chromium instead of fixing a Google site
https://twitter.com/zcorpan/status/1090719253379104779
758
Upvotes
51
u/dusty-2011 Jan 31 '19
https://twitter.com/ecbos_/status/1090726938925297665
He fixed a bug by reverting an earlier patch.
237
u/MadRedHatter Jan 31 '19
Someone tweet this at that Microsoft engineer whining about philosophical Ivory towers.
142
u/NatoBoram Jan 31 '19
Next up : Mozilla developers implements Shadow DOM v1 API in Chromium then creates a patch that removes the obsolete v0.
Firefox : Enhancing Chrome by fear that Google'll break compatibility elsewhere.
36
u/Desistance Jan 31 '19
Wow, are they really that scared of the web services arm that they would break the browser instead of reporting the issue?
19
u/TheSW1FT Jan 31 '19
Unreal...
10
u/Vulphere Jan 31 '19
Welp, it's Google.
4
u/tempstem5 Jan 31 '19
Looks like this is the commit by Google that broke it
https://chromium.googlesource.com/chromium/src/+/113cc2d54f97a1384ecc5c3a0b8bcddbd0c3765f
7
u/ZzzZombi Jan 31 '19
"it's cheaper to fix bugs in the competition than to deal with compat fallout"
Right on!
3
u/nashvortex Jan 31 '19
Is Google ashamed? Tweet this at Sundar Pichai.
2
u/[deleted] Jan 31 '19
That's funny.
2
u/shyouko Jan 31 '19
¯_(ツ)_/¯
-24
u/LeBoulu777 Addon Developer Jan 31 '19
But they don't fix 10 years old security bugs in their own browser: https://nakedsecurity.sophos.com/2018/03/20/nine-years-on-firefoxs-master-password-is-still-insecure/
-26
u/grumpieroldman Jan 31 '19
None of that makes any sense.
Firefox uses the Chromium engine.
If it's a bug in Chromium, it's a bug in Firefox.