winclassic/msfx

A Internet Explorer 5 theme for Mozilla Firefox.

msfx's Issues

Suggestions for more accuracy and improvement

Well, this is like my wish list, not a request.

• Add shortcut underline to address bar title.
• Add drop-down marker to back and forward buttons. (it's enough even if it's being a decoration)
• Add option to switch which to use site's own favicon or built-in IE icon in address bar.
• Styling favorites and history lists opened from toolbar.
• Make pop-up window toolbar more accurate like original one. (I can't remember how it did look in IE5 though)
• Add XP IE6 style support.

MSFX wont apply

I used to have the IE7 theme but then I deleted it, but I restarted Firefox and still have it after applying the MSFX5 theme

Color issues

There appears to be multiple issues with how the browser handles certain classic theme colors, which wouldn't appear when using a default theme

The bars at the top and bottom use the wrong colors, using the Window Color instead of the 3D elements text color.


Address Bar Colors just seem kinda messed up in general. I don't know if I just made bad colors for IE5, but the address bar's dropdown doesn't change color. This makes it impossible to see the autofill results with a theme that uses a white message font.

Current issues from the Firefox 109 Beta.

Ever since Firefox 108 break the tabs a fair bit in MSFX, I've decided to install the Firefox 109 beta to see what's broken on MSFX. Turns out, it's a fair bit.

• The statusbar does not work. Because, the DOM element (#browser-bottombox) no longer exists on 109. I'm either going to create the "Internet" status bar sections on #statuspanel or recreate #browser-bottombox using JS
• Context menus are completely broken. Firefox 109 now forces non native context menus, even on classic theme. This can be fixed by going to about:config and setting browser.display.windows.non_native_menus to 0. I've already put work into theming the non native context menus look like the classic theme context menus. It's going to be in the backburner until Mozilla decides to remove that about:config preference (which they will).

Even though Firefox 109 is set to release during January of 2023, it's still better if I work on these issues beforehand. Most of the minor issues have been already been fixed on the latest commits.

When toolbar icons tinting is disabled some of the toolbar icons are grey and others are colored

Desired effect: all grey as in previous versions.

Any reason why profile autoconfig is not used?

Rather than having users manually open about:config to change preferences, you can, in fact, include the preferences near the top of config.js

If I knew how to use git or do pull requests, I'd have done one. However, I don't. So instead, I'll simply recommend making the following changes to the config.js that you instruct users to put in the Firefox root folder. Simply add these lines below the //first line and above the try{}

pref("toolkit.legacyUserProfileCustomizations.stylesheets",true);
pref("svg.context-properties.content.enabled",true);
pref("ui.prefersReducedMotion",1);
pref("browser.display.windows.non_native_menus",0); 

These will automatically set the same preferences that the end user would set manually, and it automatically sets these preferences every time the browser restarts.

Optionally, you can also pre-configure other sensible default options using defaultPref instead of pref, which will only change an option if it hasn't been set or if the user resets their preferences to default. This is less obtrusive as if a user decides they really actually did want their tabs in the title bar or their UI density to be touch, they can set those options and the configuration script will not override them. As an example, the following four items pre-configure the settings I typically set when I enable this theme, which greatly speeds up installation whenever I need to set up a new profile:

defaultPref("browser.tabs.inTitlebar",0);	// Tabs seperate from title bar
defaultPref("browser.tabs.firefox-view",false);	// Disable firefox view button
defaultPref("browser.uidensity",1);		// Compact mode. 1=Compact, 0=default, 2= touch
defaultPref("browser.toolbars.bookmarks.visibility","always"); //Bookmarks bar always visible. Options are "always" "never" and "newtab"

Doing the above will simplify the installation and remove an obvious point of failure as users would only have to copy files to the root and profile directory and not have to add preferences to about:config.

The close tab button on active tab is too high

Broken Taskbar

The classic taskbar does not display. Unsure if this is related to being on Firefox version 117.

I can't access my extensions

If i want to change something for my extensions, I can't because there's no button for them Pls help

The downloads button is bigger than others and shifted.

This is using release 2.0