chappie

My comments were primarily about body copy. Headlines start off oversized and can therefore take some diminution without losing legibility – although the original reason for choosing a certain size for a display font will be compromised if it gets smaller while the body copy remains the same size (to maintain legibility). But where it is essential for display text to be smaller in smaller viewports, eg in the text panels on sliders, Customizr builds the scaling into the theme.

I’m a novice web designer but an expert reader. If I alight upon a website which is difficult to read – for any reason – I remove myself instantly. That applies to probably 80% of the sites I visit.

Web browsers enable readers to set their own preferred font and text size and it takes typical designer arrogance to force feed them something they like less – although we have all done it.

The argument for specifying neither font nor size in a website design is made here and it’s compelling.

But designers are conceited. They want people to see their creation exactly as they conceived it and if that means forcing unwanted fonts or illegible text sizes down readers’ throats, then too bad.

If you must pre-determine font and size, at least choose a size which is easy for most people to read. I see plenty of people viewing from a similar distance all the devices that websites are served up on. Most home users don’t have the space or the furniture to allow them to sit the recommended distance away from a desktop monitor so their eyes are as close to that screen as they are to a tablet or smartphone. So why force a different body copy text size on them?

Well, there’s a big debate to be had here. The trouble with scalability is that your eyes don’t scale – so by and large, the optimal font size for legibility on a large screen will still be the optimal size on a small screen. Otherwise, when a smart phone reduces your page width by 90% your 10pt font would reduce to 1pt and be illegible.

So, ideally you want your fonts not to scale (much) if you want your text to remain easy to read. Yes, your page design will be compromised somewhat by reflowing etc but that’s an acceptable trade-off whereas illegible text would not be.

You probably have to accept that your site will look very different on large and small screens – which, by and large, WordPress and Customizr handle well automatically.

But here’s some more on font measurement …

Try this.

= 3.2.10 December 23rd 2014 =
43 * f404eda Add a fallback false value to tc_user_started_before_version()
44 * 1577dfb Add Google fonts to the theme description
45 * 349ee57 Merge branch ‘eri-trabiccolo-fix_tccta-in-subpanel’ into dev
46 |\
47 | * 72d22a6 Merge branch ‘fix_tccta-in-subpanel’ of https://github.com/eri-trab| |\
48 |/ /
49 | * be4b067 Fix: ‘hide’ tc-cta when in sub-panel
50 * | 7414a5e Fix the double title bug add backward compatibility with wp_title()

Thanks/merci @nikeo for the Christmas present/cadeau.
Merry Christmas/Joyeux Noel to one and all/tout le monde.

kgueter1, there are two things you can do to ameliorate the problem:

1. Frame your slider images so that the parts of it liable to be lost from view are non-critical;

2. Use a framed slider rather than full-width. Only full-width sliders keep growing as the page widens beyond 1200px: framed sliders will just centre themselves within ever wider borders.

?? How quickly one forgets. At least, this one does.

I’ve amended the image subject matter to allow for expansion/contraction.

Thanks d4z_c0nf.

@electricfeet – it ain’t really fixed until you tell me it’s fixed ??

Thank you @nikeo – Customizr .24 update has fixed this problem (from where I sit at least). Sliders display much more quickly without the revolving progress thingy – and instantaneously once cached.

Marked as resolved.

Thanks, ElectricFeet and…

YIKES! SIX seconds!!??

Have you upgraded?

Thank you, Dave. I get closer to 2 secs every time in Mac Safari, albeit Mac Firefox and Mac Chrome are a fraction quicker.

I’m hoping the fix won’t involve forcing each visitor to flush their cache as this would somewhat negate the benefit of serving cached pages in the first place!

I’ve re-cached all my pages via my plugin and I’ve cleared my browser cache but I still get a delay of 1-2 seconds while the slider loads (spinning icon) which I haven’t seen before the latest upgrades. Could someone please tell me if new visitors see it, e.g. on this page?

Thanks.

When I upgraded earlier this morning, I too had initial problems which mostly went away by themselves. These were:

– Front end sliders not advancing
– Back end Customizr menu>Widgets completely blank
– Back end Customizr page preview showed permanent spinner but no slider images
– Back end Customizr page preview drop down menu disappeared behind slider spinner overlay

Logging in and out a couple of times seemed to fix most of the issues.

bundewarius, your slider works fine for me (the spinning wheel does appear for a fraction of a second but then the images load and advance as they should).

Could you be seeing a local cache issue?

There are a couple of convenient free online tools for re-sizing images. I haven’t used them but you could give them a try. Read the Help/FAQ pages first:

https://www.imageoptimizer.net
https://www.webresizer.com

The required size for a slider is typically 1170 x 500 pixels. Try to keep critical subject matter away from the edges.