[tiago]

Guys,

I managed to fix the margins, but now the columns are being thrown to the left, instead of centering them on the page :/
I’m not sure how to fix this, I’m guessing that trying to compensate “manually”, with different left right margins, might cause issues in different screen resolutions.

Can you help?

Tiago

Attachments:

You must be logged in to view attached files.

[tiago]

OK, managed to fix it changing padding to margins and and defining negative margins to the column extra class.

Do you think you will fix this issue in a future update? Because if you do, then we would have to reverse the changes…

[tiago]

This reply has been marked as private.

[tiago]

This reply has been marked as private.

[tiago]

Hi Ed,

To be honest I haven’t really tested to see how that feature behaves, since I had removed it to leave detail pages lighter, and how often it may end up showing already viewed posts in a single author’s blog. I’ll have a look at it. I did test one plugin, but didn’t work. I’ll keep my fingers crossed hoping you can sneak that option in.

Thanks again.

[tiago]

Hi David,

That’s a shame. I’m doing an image-blog and was hoping not having to force visitors to use the back button or clicking on the blog menu item to go back to the main blog page. Just adds an extra click or many extra clicks if they wish to flick through.

It would be a nice feature to have.
Tiago

[tiago]

OK, cool.. At least now I’m warned.
Thanks again.

[tiago]

Just an additional note that I was reading the comments on the later article last night (always a good thing since other people may offer a different view and suggestions of improvement) and I did find a couple of comments warning against using a root % with rem.

The root % is related to the navigator’s standard font size, which for a while has been 16pt, quite big and why the author suggests using 62.5%, which is equivalent to a 10pt root.

The problem with this solution is that a user may change the navigator’s standard font size, making it smaller or bigger. This means that whatever percentage we set will apply to their custom configuration and may have a big effect on font sizes. Say the user chooses 10pt size as a standard, 62.5% root will be equivalent to 6pt, which is very small.

Instead, you can set your root size in pt or px, with the difference being in allowing the user change font sizes (pt) or only scaling the entire page (px) using the zoom tool.

Having said this, another commenter suggested that it is easier to use ’em’ than ‘rem’, since the later requires adding fallback ‘px’ sizes for older navigators, while ’em’ only requires a reset for nested lists to prevent compounding sizes.

Worth investigating deeper before just picking whatever solution.

[tiago]

Hi,

Perhaps I wasn’t clear enough. I realize you don’t take paid work (I had read it in another topic).

What I am asking is whether you think this particular change might envolve major rework for a PHP developer, since you said “it’s not possible” or whether it might me something reasonably simple.

Thanks for the links.
Tiago

[tiago]

Kyle,

If you don’t mind me asking, since you know the template better than anyone, is this something a developer with PHP knowledge might me able to resolve with relative ease or would it require big rework? I`m asking since I’ve got a couple of projects going and may hire a developer towards the end for some small but trickier fine-tuning and customizations.

Thanks again.

[tiago]

Ahhh… Pitty. Thanks anyway Kyle.

Tiago

[tiago]

This reply has been marked as private.

[tiago]

Just a p.s. correcting an earlier statement. Edge actually renders similar sizes to Chrome and IE. I hadn’t noticed, but I had the zoom set to 125% :p

[tiago]

Most welcome, Mohammad.

mhote, the following article is also quite interesting, as it explains the pros and cons of using either ‘px’ or ’em’ (no perfect solution, you have to choose the least worst) and also introduces a new unit I hadn’t heard about for CSS3; ‘rem’

https://snook.ca/archives/html_and_css/font-size-with-rem

Regards
Tiago

[tiago]

hi mhote,

I came in curious as to what the Swift team might respond to this. I don’t know how much you know about this issue… Major browsers render fonts differently, sometimes even line weights and colours. Chrome renders in a quite different size from most major browsers, generally speaking much smaller text. IE comes closest, with Edge, Opera and Firefox rendering significantly larger.

I doubt you’ll find templates that adjust to these differences automatically. For traditional typography loving print designers (like myself), initially this is a headache (heresy!), but it’s something I got to accept; that I cannot fully control type on the web (hell!).

There are a few solutions out there to minimize such differences, like using ’em’, ‘%’ or ‘px’ units on font sizes instead of ‘pt’, though some developers don’t recommend ‘px’. There is also the CSS reset, which must be tailored to your own website styles, so I guess putting this on a template-base doesn’t make sense, since a lot of people change their styles throughout.

You may find these two articles interesting:
http://stackoverflow.com/questions/521832/consistent-font-size-across-browsers-web-development
http://stackoverflow.com/questions/30876894/how-to-prevent-different-browsers-rendering-fonts-differently

Regards
Tiago