Re: How 'bout a <pre> (and other stuff) warning? (fix)

I'd rather just solve the problem by having PerlMonks render PRE blocks rather similarly (but not identically) to how it renders CODE blocks. I'd also be in favor of a toggle that turns off the wrapping tricks for those rare cases when you actually want a node rendered wider than you choose to (or perhaps can) make your browser window because you want to scroll to the left or right side and look at that part of the node without other wrapped stuff getting in the way.

I see that my quite-up-to-date version of FireFox still doesn't properly support soft hyphens so the best way to deal with this stuff is still mostly only handled by IE¹ (which follows the standard on this point, unlike FireFox, and has for many years now, in case you didn't get the irony).

BTW, if you don't like my idea, one reason certainly could be that you don't use IE and so don't have access to (a working version of) the lovely "auto code wrap" feature. It is probably a bit of work to borrow a copy of IE (or other soft-hyphening browser) and set up "auto code wrap" and play with it enough to see how lovely it works, but you might consider doing that... (:

- tye

¹ Yes, I've heard that Opera also now supports soft hyphen (and I suspect that there are other browsers that support it by now)

, but my "mostly" allows me to disregard fringe browsers. And if you take offense at my calling Opera a "fringe browser", then I instead claim that my experience with Opera leads me to believe that just because one version of Opera has fixed support for soft hyphens, it gives me only a little hope that future versions of Opera won't have re-introduced previous identical bugs that broke the handling of soft hyphen. (: The Opera team really needs to learn about automated test suites, as near as I can tell from here. There are several things that I really like about the ancient version of Opera that is the only thing available for my ancient Zaurus. But I can't resist noting how impressed I was by their ability to introduce so many basic bugs in that mature of a product. :)

Comment on Re: How 'bout a <pre> (and other stuff) warning? (fix)

Replies are listed 'Best First'.
Re^2: How 'bout a <pre> (and other stuff) warning? (fix) by blazar (Canon) on Oct 23, 2006 at 09:04 UTC
I'd rather just solve the problem by having PerlMonks render PRE blocks rather similarly (but not identically) to how it renders CODE blocks. This is an equally good and seemingly viable solution. For more stuff in this vein, I've occasionally felt the need for `<code>` blocks that still allow (some) formatting tags and/or entities, like in the [id://578807#conclusion\|case] I was referring to above, perhaps in the form of suitable attributes, like: `<code allowentities="yes" allowtags="yes" wrapoff="yes">` [download] I'd also be in favor of a toggle that turns off the wrapping tricks`[...]` I second this too, perhaps in the form of another attribute as in the example above (of course they should all default to `"no"`). The point being that the problem with `<pre>` tags is that (some) people already knows about them, and it's just so easy to insert them, whereas such attributes would be totally uncommon and annoying enough to insert that one would really do so only in those rare cases he would really need them. BTW, if you don't like my idea, one reason certainly could be that you don't use IE and so don't have access to (a working version of) the lovely "auto code wrap" feature. It is probably a bit of work to borrow a copy of IE (or other soft-hyphening browser) and set up "auto code wrap" and play with it enough to see how lovely it works, but you might consider doing that... (: Actually I have Exploder installed but use exclusively FF. You made me curious about this "lovely feature" and I think I will try, but I won't change my browser anyway. Only I will hope the FF guys will implement something similar soon too!	[reply] [d/l] [select]
Re^3: How 'bout a <pre> (and other stuff) warning? (fix) by tye (Sage) on Oct 23, 2006 at 14:32 UTC
I'd also be in favor of a toggle that turns off the wrapping tricks I second this too, perhaps in the form of another attribute as in `<code allowentities="yes" allowtags="yes" wrapoff="yes">` No, turning off wrapping has to be selected by the viewer, not by the author of the node. - tye	[reply] [d/l]