Re: HTML_FONT_SIZE_HUGE firing on html that looks ok

On Tue, May 12, 2026 at 03:42:01PM +0200, Matija Nalis wrote:
> IMHO, the best solution would be for 4.x codebase to create separately
> named evals for 4.0.x sizes, e.g. `min_size_pt` and `max_site_pt`
> 
> and then have rules:
> 
> body HTML_FONT_SIZE_HUGE_LEGACY    eval:html_range('max_size', '6', 'inf')
> body HTML_FONT_SIZE_HUGE_PT        eval:html_range('max_size_pt', '24', 'inf')
> meta HTML_FONT_SIZE_HUGE HTML_FONT_SIZE_HUGE_LEGACY || HTML_FONT_SIZE_HUGE_PT

Alternatively (and likely much better, now that I think of that), one
could simply update just the rules:

if (version >= 4.000000)
body HTML_FONT_SIZE_HUGE    eval:html_range('max_size', '24', 'inf')
endif

if (version < 4.000000)
body HTML_FONT_SIZE_HUGE    eval:html_range('max_size', '6', 'inf')
endif


(exact version could me modified if it happened in some specific
version, but 3.6 vs 4.x is probably good enough)

> Someone should open a bugzilla issue (and mention it here, so
> interested parties may follow. I unfortunately can't do it at the
> moment)

-- 
Opinions above are GNU-copylefted.