Am I the only one who hates optimizing stuff for chrome?Some examples>make 100px div>it's 100px in every browser>somehow it's 108px in chrome>need to add extra rule to fix it>make normal table with minimal styling>works perfectly fine in every browser>chrome adds random line breaks and spacings>need to add extra rule to fix it>make simple form with minimal styling>looks good in every browser>chrome randomly stretches and line breaks the inputs, looks terrible>need to add extra rule to fix itAnd that's just the basic stuff, the more you add the worse it gets. Chrome doesn't respect any web standard and just randomly shits itself all over the place. At this point literally 30% of my code is just there to fix stuff in chrome and it's fucking frustrating. I can't be the only one noticing this. Total chrome death.
>>100122662>Chrome doesn't respect any web standardChrome is the web standard, have you not learnt?
>forcing webshits to work twice as hard wtf based, i love google now
>>100122662In my opinion, you're extremely retarded.
>>100122673>>100122682>>100122750Since when are Google shill bots so blantant?
>OP hated them because they told him the truth.
>>100122662Skill issue
>>100122940I hate Google, I'm just a realist
>>100122662Holy fuck just write sementic HTML and submit a bug report if it's messed up. Don't do Google's job for free.
>>100123894What do you mean? I write w3c valid html and chrome still shits up everything. Report where? Like they care about some small shitty webdev
>>100123974>Report where?with a truckload of anfo at google hq
You webshits have someting named reset.css or something right
>>100122662>Am I the only oneYes. I don't even test on Chrome. Actually I only test on Firefox.
This is not an issue at all if you just only target chrome.Fuck the other browsers, they aren't needed anyways.
>using regular chromeSee that was your first mistake.
>>100122662>make 100px div>it's 100px in every browser>somehow it's 108px in chrome>need to add extra rule to fix itStopped reading there, probably there's something fucked up in your code or you are using a ton of 3rd party shit that you don't even know what it does.
>>100123974>I write w3c valid html and chrome still shits up everythingNo you don't and no it doesn't you retarded brown nigger. Kill yourself.
>>100122940Is he wrong? You're setting out coding for the wrong browser and then trying to loop it into the mix afterwards. Also this >>100124050You shouldn't even be having this problem in the first place if your environment was setup properly
>>100126601I use zero third party code.>>100124050>>100127985These don't do shit especially not against the random line breaks.>>100126975Stay mad Google shill
>>100129078You're the problem.
He's right, Chrome is the new Internet Explorer 6, but you kids are too young to understand what it means.
>>100129280IE was stalling the web and didn't follow more standards than their own, a chrome monopoly is bad but not in the same way as IE times.
>>100129410>but not in the same way as IE times.No, it's worse. Because it's trying to introduce standards that maximize their profits. Like making adblockers worse. See Web Extensions V3, or the "Web Environment Integrity API".
>>100129529Web Extensions V3 is not a web standard nor required to make any site work on any browser, is like calling the old firefox jetpack sdk a web standard.
>>100129171I don't use chrome
>>100122662skill issue
>>100122662>>make 100px divstopped reading here>>still using pixel
>>100131755It was just an example
>>100122662DevTools on Google Chrome Stable indicate pic related is 100x100px. Do you have any code examples showing this weird 108px div behavior.
>>100132756tsmt. op hasn't posted a single shred of evidence for his 108px woes.
>>100132756He's probably using a border and not using box-sizing or something like that... all browsers has the sizes figured out long ago the last time I've seen a browser ignoring a standard in an ancient feature has been in the initial edge before it was based on chromium and it was an obscure small part of js that almost nobody used.
>>100131005Are you the only person that will be using the website that you are building? Because that's the only way that your edgelord response would ever matter
>>100132893The edge issue was that lastIndex on the RegExp.prototype.test() was always being reset even when it returned true.
