fixed up dark gtk post to use nested quotes

_posts/2019-02-28-18th-year-old-firefox-bug-web-page-controls-are-unreadable-if-you-use-a-dark-gtk-theme.markdown

@@ -23,9 +23,9 @@ The issue is web developers assuming that input fields are always light colored,
 
 Use [Fix Dark Theme Input Boxes](https://addons.mozilla.org/en-US/firefox/addon/fix-dark-theme-input-boxes/) to override this.
 
-> <q>It's more of a web bug than a Firefox bug.</q>
+> > It's more of a web bug than a Firefox bug.
 >
-> That may technically be true, but the bottom line is I've never had this problem with any other browser.
+> That may *technically* be true, but the bottom line is I've never had this problem with any other browser.
 
 That is because other browsers don't bother to integrate with your GTK theme. Firefox gets burned here because it tries to be a good platform citizen. It is probably going to be "fixed" by [bug 1411425](https://bugzilla.mozilla.org/show_bug.cgi?id=1411425 "[meta] [gtk] [fission] Remove full-native theming for content (Linux NNT)") so whatever.
 
@@ -43,7 +43,7 @@ Native theming has been part of web browsers forever -- I know Safari had it, Ne
 
 > your initial assertion was they were doing it to be a good platform citizen, and it's retarded to do something that allows a common platform choice to break the web, if you're a web browser.
 >
-> <q>Native theming has been part of web browsers forever -- I know Safari had it, Netscape had it, Camino had it - even IE had it.</q>
+> > Native theming has been part of web browsers forever -- I know Safari had it, Netscape had it, Camino had it - even IE had it.
 >
 > and to my knowledge, they didn't break the web because they didn't make stupid decisions and then ignore user complaints for a decade.
 
@@ -55,7 +55,7 @@ When sites don't override form widget styling, everything works fine. It is only
 
 No other OSes have had native dark theming until very recently. It would be impossible for them to ignore user complaints for a decade if the users never complained because they never had access to dark themes in the first place.
 
-> <q>When sites don't override form widget styling, everything works fine</q>
+> > When sites don't override form widget styling, everything works fine
 >
 > unless they set the font color. even then, that's a big if. considering that a pretty large majority of websites get fucked by this bug.
 >
@@ -65,7 +65,7 @@ No other OSes have had native dark theming until very recently. It would be impo
 
 So you dropped the argument that the web has a standard spec for widget/control theming that is separate from OS styling?
 
-> <q>So you dropped the argument that the web has a standard spec for widget/control theming that is separate from OS styling?</q>
+> > So you dropped the argument that the web has a standard spec for widget/control theming that is separate from OS styling?
 >
 > no. since we both agreed that there is no spec that says OS style has to propagate into the web rendering engine, i don't understand what you're trying to argue about.
 
@@ -81,15 +81,15 @@ So you agree that it is web authors that are breaking their own websites on mino
 
 (yes, I am using a dark theme on Linux, and yes, all of those examples are themed appropriately.)
 
-> <q>So you agree that it is web authors that are breaking their own websites on minority OSes because they don't realize that browsers on those OSes may respect the users wishes that controls are themed according to their OS theme, right?</q>
+> > So you agree that it is web authors that are breaking their own websites on minority OSes because they don't realize that browsers on those OSes may respect the users wishes that controls are themed according to their OS theme, right?
 >
 > no. tons and tons of websites are broken because of a team effort between web designers not doing perfect theming and firefox not doing its job of rendering websites sanely. it has very little to do with the OS, because the OS simply passes information to the web browser.
 >
-> <q>you seem to be the one with the chip on your shoulder.</q>
+> > you seem to be the one with the chip on your shoulder.
 >
 > i didn't refer to a bug fix as a bug "fix"
 
-As I mentioned previously, native theming has been around forever. Clearly, you prefer that browsers not theme themselves based on the OS that they run on. In that case, you can change the preference.
+Native theming has been around forever. Clearly, you prefer that browsers not theme themselves based on the OS that they run on. In that case, you can change the preference.
 
 I don't get the anger, personally.