On Sat, 5 Nov 2016 21:24:47 -0500
Leslie Turriff <jlturriff@...> wrote:

> On 2016-11-05 01:53:11 Nick Koretsky wrote:
> > On Sat, 5 Nov 2016 00:28:06 -0500
> >
> > Leslie Turriff <jlturriff@...> wrote:
> > > > Because the easiest ways to deal with firefox is chrome/userChrome.css
> > > > file in you firefox profile or "Theme Font & Size Changer" addon.
> > >
> > > 	You appear to misunderstand my request.  I'm not (as much)
> > > concerned with the content of web pages as the fonts used to display file
> > > pickers, configuration dialogs, menus, etc., components of Firefox
> > > itself.
> >
> > Firefox GUI is written ix XUL and can be edited with css markup using that
> > file (or addons)
> 
> 	So I started looking for information on XUL, and found this:
> https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL/Tutorial/Modifying_the_Default_Skin
> which might fit the bill, but seems to be talking about Chrome, not Firefox.

Google hijacked the name "Chrome" comparatively recently.  Before that, it was 
sometimes used to refer to the appearance of a program.  The names of those Firefox 
files and directories go back more than a decade, to when Google was just a little
baby search engine. ;)

> 	I also ran across this:
> http://www.zdnet.com/article/mozilla-changes-firefox-apis-developers-unhappy/

Yes, the Mozilla devs have announced their intention of dropping XUL, but they haven't
actually done so yet.  Palemoon will be keeping it, so there will still be a XUL-based 
browser available.

Firefox's UI fonts on my system are still responding to either my GTK2 or GTK3
configuration files and coming up as 12-point Times New Roman, but I have no
idea which file it's answering to or how long it will continue doing so (and some other
UI elements, like the "searching for updates" progress bar, were not displaying
correctly when I opened the browser to test that, so its GTK support is messed up
again in some way).

E. Liddell