3 ms·

Anecdotally, about half the frontend bugs that I see go through our JIRA at work seem Safari/iOS specific lol

by folkrav 4y ago

bzzzt 4y ago
Probably because all the frontend people are using Chrome, so those bugs were already fixed.
- simondotau 4y ago
  It’s ironic that the people who hate dealing with Safari are, though they would never admit it, actually complaining because they resent having to test in more than one browser. Let’s just throw in the towel now and rename the web to the Chrome Platform.
  - creeble 4y ago
    Or resent having to pay Apple to test in their browser.
    - simondotau 4y ago
      That’s simply wrong. You don’t have to pay Apple. Safari is just WebKit and WebKit browsers are available for Linux. Or depending on your tolerance for legal grey areas, you can also download MacOS directly from Apple servers and run it in a virtual machine. Or if your objection isn’t to paying money but rather paying Apple, you can buy second-hand hardware.
    - deleted 4y ago
      [deleted]
    - selectodude 4y ago
      Good news! Microsoft makes a Webkit browser that's up to date with Safari's webkit version. https://github.com/microsoft/playwright https://github.com/microsoft/playwright
jalk 4y ago
And about the other half is for chrome, and the rest is for all other browsers or what?
coldtea 4y ago
Seeing that Safari/mac/iOS and Chrome/blink (so also Edge/Opera) are the only game in town adoption wise (FF has fallen way below), how else would it be?
- recursive 4y ago
  Those that aren't browser specific, unless this is some kind of trick question.
  - coldtea 4y ago
    I don't think the parent refers to/includes non-browser based bugs...
    - recursive 4y ago
      When I said "browser specific", I meant "referring to a specific browser", not "relating to browsers".
      - coldtea 4y ago
        Yeah, I got what you meant. Probably didn't word my answer well: by "Non-browser based bugs" I mean bugs caused by the code of the webpage having logic issues/bugs (as opposed to bugs caused by browser JS issues or CSS/HTML implementation incompatibilities and such). Perhaps "browser-engine-related" would be a better term So, I read the parent comment as referring to browser-engine-related bugs - things caused by a browser engine behaving differently, not implemented, etc, and not including in his numbers regular webpage bugs due to html/js programmer error.
        recursive 4y ago
        If there's a logic error in the visibility of a button, I would classify that as a "frontend bug".

Anecdotally, about half the frontend bugs that I see go through our JIRA at work seem Safari/iOS specific lol

bzzzt 4y ago

Probably because all the frontend people are using Chrome, so those bugs were already fixed.

simondotau 4y ago
It’s ironic that the people who hate dealing with Safari are, though they would never admit it, actually complaining because they resent having to test in more than one browser. Let’s just throw in the towel now and rename the web to the Chrome Platform.
- creeble 4y ago
  Or resent having to pay Apple to test in their browser.
  - simondotau 4y ago
    That’s simply wrong. You don’t have to pay Apple. Safari is just WebKit and WebKit browsers are available for Linux. Or depending on your tolerance for legal grey areas, you can also download MacOS directly from Apple servers and run it in a virtual machine. Or if your objection isn’t to paying money but rather paying Apple, you can buy second-hand hardware.
  - deleted 4y ago
    [deleted]
  - selectodude 4y ago
    Good news! Microsoft makes a Webkit browser that's up to date with Safari's webkit version. https://github.com/microsoft/playwright https://github.com/microsoft/playwright

jalk 4y ago

And about the other half is for chrome, and the rest is for all other browsers or what?

coldtea 4y ago

Seeing that Safari/mac/iOS and Chrome/blink (so also Edge/Opera) are the only game in town adoption wise (FF has fallen way below), how else would it be?

recursive 4y ago
Those that aren't browser specific, unless this is some kind of trick question.
- coldtea 4y ago
  I don't think the parent refers to/includes non-browser based bugs...
  - recursive 4y ago
    When I said "browser specific", I meant "referring to a specific browser", not "relating to browsers".
    - coldtea 4y ago
      Yeah, I got what you meant. Probably didn't word my answer well: by "Non-browser based bugs" I mean bugs caused by the code of the webpage having logic issues/bugs (as opposed to bugs caused by browser JS issues or CSS/HTML implementation incompatibilities and such). Perhaps "browser-engine-related" would be a better term So, I read the parent comment as referring to browser-engine-related bugs - things caused by a browser engine behaving differently, not implemented, etc, and not including in his numbers regular webpage bugs due to html/js programmer error.
      - recursive 4y ago
        If there's a logic error in the visibility of a button, I would classify that as a "frontend bug".