.. -=- 910CMX style fixes and tweaks -=-

# 910CMX style fixes and tweaks.

[This is the userscript as a Gist. Click `Raw` to install it.](https://gist.github.com/harjitmoe/9b51a25fa8ac523cc29042f9cbc3dbf0) You need to have first set up compatible userscript manager (see below) for this to work. You may need to enable the script following installation.

.. html-a::
   :href: javascript:var aggga=document.createElement('link');aggga.setAttribute('rel','stylesheet');aggga.setAttribute('href','http://harjit.moe/css/x910.css');document.body.appendChild(aggga);void(0);

   Alternatively, here is a bookmarklet which loads the stylesheet (don't click it here, add this link to your bookmarks and run it on the forum page).

Userscript managers:

- Greasemonkey works (available [for Firefox(^:kome:^)](https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/) and [for SeaMonkey](https://openuserjs.org/about/Greasemonkey-Port-for-SeaMonkey)).
- [Tampermonkey](http://tampermonkey.net/) can run the scripts in Chromium (hence Google Chrome), UC Browser and Firefox;(^:kome:^) this claims to also work for Edge, Safari, Opera Next, and Dolphin, although I haven't tested it with those ones (nor with UC Browser for a long time).
- [This compatibility script](https://github.com/epitron/scripts/blob/master/opera-scripts/aagmfunctions.js) provides an implementation of ``GM_addStyle`` for Opera, apparently allowing that script to be used with that browser's built-in userscript manager (although I haven't personally tested this, I am so informed).
- Chrome (certain versions at any rate) may also support installing user-scripts as extensions. [Further info](http://stackoverflow.com/questions/5258989/manually-adding-a-userscript-to-google-chrome). I have not tested this.

 :kome: Regarding Firefox for Android: as part of Mozilla's bizarre hellbent conviction toward burning any and all of Firefox's competitive advantages one by one, addons besides a small list of "recommended" addons are no longer available in the Android release, with using a custom list instead being [hidden as a secret feature, in the separately-IDd Android nightly version](https://blog.mozilla.org/addons/2020/09/29/expanded-extension-support-in-firefox-for-android-nightly/).

---

Historic content from this page. '''I am not sure to what extent it still applies.'''

>! Essentially, there is a rule in the CSS stylesheet (the file defining the layout and formatting of the page) that turns certain text white (in spite of the white background). This rule's selector appears to apply to paragraphs in the rich text editor when it is created from the "edit post" function as opposed to replying.
>! 
>! Solutions without custom scripts or stylesheets:
>! 
>! - Format the post content (I'd suggest excluding links) explicitly black, rather than "automatic", thus overriding the defective stylesheet. Short of being able to set up the Greasemonkey solution below, this is probably the best solution. [(1)](http://community.910cmx.com/index.php?/topic/33-what-are-you-doing-right-now/&do=findComment&comment=10740) [(2)](http://community.910cmx.com/index.php?/topic/287-np-wednesday-july-27-2016/&do=findComment&comment=11007) However, the button for this might not show on mobile devices / tablets. [(3)](http://community.910cmx.com/index.php?/topic/287-np-wednesday-july-27-2016/&do=findComment&comment=11255)
>! - Use the HTML editor. Which can be a pain, but it is unaffected.
>! - Selecting text, making the white text visible against the highlight. Temporarily, of course. This is the most obvious solution, but a last resort in terms of usability.
>! - Converting text to a bulleted list, causing the selector of the problematic CSS rule to no longer apply to it.
>!
>! Custom scripts:
>! 
>! - [This small script](https://gist.github.com/harjitmoe/de3b85c909a6093e6e0458f29c54bc7a/raw/a271a46decc73153f2152a553ec07f8718f29282/910-white-fix.user.js), which overrides the rule in question.
>! - [A more extensive version](http://community.910cmx.com/index.php?/topic/657-forum-interface-fixes-greasemonkey-wrapped-custom-stylesheet/) which also fixes many other aspects of the interface CSS, but may break things it if any interface changes occur.