Font size in posting field

[kirkmc]

It got smaller; it's quite small, actually, and it's light, which makes my aged eyes have to squint to read it... Could it be increased? Maybe not as big as it was before - it was quite big - but somewhere in between?

[Solomon]

In the event that an increase in font size is implemented and you still find it too small or the font size change isn't implemented at all, you can always ⌘-+ to increase the font size (though it increases the font size for everything else as well). If you were already aware of this, hopefully other OS X users will find the tip useful.

[kirkmc]

In the event that an increase in font size is implemented and you still find it too small or the font size change isn't implemented at all, you can always ⌘-+ to increase the font size (though it increases the font size for everything else as well). If you were already aware of this, hopefully other OS X users will find the tip useful.

Yes, I am aware. And I've done that. It skews the page, though.

[fwiffo]

It got smaller? When I made the changes to fix Safari, it got bigger on my screen.

[kirkmc]

It got smaller? When I made the changes to fix Safari, it got bigger on my screen.

About half the size here. It was pretty big before; I'd say 16 pt. Now it's tiny, like fonts developers use.

[fwiffo]

You're using Safari, right? I've made a change that may help, give it a refresh...

[kirkmc]

You're using Safari, right? I've made a change that may help, give it a refresh...

Yes, Safari on Mac.

Here's what I see.

[Joaz Banbeck]

On firefox, it appears no bigger, maybe smaller. But the spacing is much better.

[fwiffo]

Alright, I made another change, please give it a hard-refresh and let me know if that's better. Safari is known to have some strange behaviors with monospace fonts, but this might get around it. If not, I'll have to probably use a browser-detecting hack, which I am loathe to do.

I wish I had a Mac at hand to test this on because debugging web stuff this way is insane.

[topazg]

Alright, I made another change, please give it a hard-refresh and let me know if that's better. Safari is known to have some strange behaviors with monospace fonts, but this might get around it. If not, I'll have to probably use a browser-detecting hack, which I am loathe to do.

I wish I had a Mac at hand to test this on because debugging web stuff this way is insane.

Can't you get a Mac virtual machine for whatever OS you're using?

[kirkmc]

Alright, I made another change, please give it a hard-refresh and let me know if that's better. Safari is known to have some strange behaviors with monospace fonts, but this might get around it. If not, I'll have to probably use a browser-detecting hack, which I am loathe to do.

I wish I had a Mac at hand to test this on because debugging web stuff this way is insane.

That's better, but why are you using a monospace font? It's ugly.

[xed_over]

That's better, but why are you using a monospace font? It's ugly.

its to solve another problem -- editing diagrams

[kirkmc]

That's better, but why are you using a monospace font? It's ugly.

its to solve another problem -- editing diagrams

You mean people don't do diagrams in another program and paste them in their browser for the forum? That's how they must have done on GD.

[xed_over]

You mean people don't do diagrams in another program and paste them in their browser for the forum? That's how they must have done on GD.

I can't really speak for people, but I don't

If new, I copy-paste from another thread and modify

Otherwise, I edit in place a previously submitted post <-- this is really what the fix is in place for, reediting one's own post (or editing a quoted post).

[fwiffo]

I always edit diagram code as text. Occasionally I'll do that in vim instead of the browser's text area because it has column selection, but I don't use a go program to make diagrams unless they're extremely complicated. It's usually faster to edit them as text.