comment on

> (If I had the time, I might even look at the routines that filter the nodes' HTML, to see if those tags could be rejected automatically for AM posts

that could be generally done by patching approved html tags °

I suppose it might create backwards compatibility issues.

Also coding an exception for AM is feasible, but I'm shying away from making things more complicated.

> Or look at whether there might be some CSS changes possible to mitigate the effect.)

Most of our culture is from a time where not all clients supported CSS.

I think a logarithmic scale would be nice.

But I have to admit that my settings don't always render reliably on mobile-chrome ...

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

°) looks like I accidentally did submit a patch, no idea how this happened.(?)

In reply to Re^5: Petty janitor post vandalism by LanX
in thread Petty janitor post vandalism by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks