Bug in 2.1.5-RELEASE GUI (edit: clear your browser cache!)

[slu]

Thanks for testing.

Missing font problem?

[kejianshi]

No idea.  I suspect its purely a cache problem.  Like for whatever reason, your browser is holding onto data that is messing things up for you.

[slu]

Found it!

On my Debian system was some more fonts, as well the "Verdana" font.
https://packages.debian.org/wheezy/ttf-mscorefonts-installer

I replace in the all.css fiel the following lines:

html, body, td, th, input, select {
    font-family: Tahoma,Verdana,Arial,Helvetica,sans-serif; <----- from
    font-size: 0.9em;
}

html, body, td, th, input, select {
    font-family: Tahoma,Arial,Helvetica,sans-serif; <----- to
    font-size: 0.9em;
}

And it work fine!

[kejianshi]

Thats cool - But I suspect if there wasn't something weird going on with the new pfsense gui, we wouldn't have ever noticed such problems.

[slu]

The "Verdana" font does not feel well on Debian Linux  ;D
I guess the spacing is a little bit different which results in this broken gui.

[itzo]

when here is unchecked everything is OK …


[slu]

Which is in the end the similar problem.  :)

[jdillard]

@slu:

Found it!

On my Debian system was some more fonts, as well the "Verdana" font.
https://packages.debian.org/wheezy/ttf-mscorefonts-installer

I replace in the all.css fiel the following lines:

html, body, td, th, input, select {
    font-family: Tahoma,Verdana,Arial,Helvetica,sans-serif; <----- from
    font-size: 0.9em;
}

html, body, td, th, input, select {
    font-family: Tahoma,Arial,Helvetica,sans-serif; <----- to
    font-size: 0.9em;
}

And it work fine!

This is correct. Tahoma isn't included on some operating systems. Veranda is intended for "fine print" type design applications and is a wider font, thus pushing the menu out.

[Supermule]

But why run a fixed width menu and not something that adjust to simple things like that?

[jdillard]

you'll have to ask whoever designed it…it's an open source project.

[Supermule]

HAHAHAHAHAHAHA :D

Maybe you could point me in the right direction??

@jdillard:

you'll have to ask whoever designed it…it's an open source project.

[jdillard]

https://github.com/pfsense/pfsense/commits/RELENG_2_1/usr/local/www/themes/pfsense_ng/all.css

behold the power of git!

[Supermule]

Get on with it then :D

A side note Jared… Would be great if you could redo the pfsense webgui so it worked well even with different fonts and browsers...

[jdillard]

I'll be working a fix into master for future releases, it's hard to plan for missing fonts. The trick with working on the current (note I said current) GUI is knowing when to stop fixing things ;)

[Supermule]

Charlie did the widescreen for me and has made a lot of changes to the CSS and code to make it really nice.

Charlie440 is his name in here. Could be that you should talk to him.

[Guest]

@kejianshi:

No idea.  I suspect its purely a cache problem.  Like for whatever reason, your browser is holding onto data that is messing things up for you.

This.

The CSS changed, and browsers have a tendency to cache the CSS.

[Paul47]

I'm seeing this with Seamonkey on Lubuntu. In my case, simply reloading the page put the help menu back where it belongs.

[Synthetickiller]

I have yet to run into the issue here, but I'm running 1440p monitors on Win 7.

[thedude42]

In case anyone hasn't figured it out, if you are using a browser that has some kind of developer options that allows you runtime access to the style information on the page, you can open up those tools and edit the style so you can temporarily navigate to one of the menu items under the "System" menu.  This works quite well for me in chrome.

Basically you find the style entry mentioned previously:

font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;
font-size: 0.9em;

All I did was change the .9 to .8, and it shrank all of the menu fonts enough that I could access the drop down menu.

This was a quick and easy work-around that did not require me editing any of the system files on pfsense, for people looking for something along those lines.

[w0w]

In my case I've changed active theme twice - to something else and back to original and my problem is gone. You can see what was wrong on attached image - 2.1.5 is on the left side and 2.2 Alpha is on the right, two browser tabs opened in one browser simultaneously and sreenshots are taken and compiled into one image.