Hi All

I happened to read and test the formatting tips suggested at the end of every text editor while creating or replying a node and i found the following..

Bug Definition : All text outisde the text editor goes to small font/formatting if <pre> is used before and after text typed.

Step to reproduce

1) type some text and prefix <pre> and suffix <pre>tag and press the Preview radio button.<p>

2) ( OR ) Type some text with various other formatting and finally for the last but one sentence end it with '

"write something" <pre>

3) Press the "preview" radio button and view the text outside the text editor ( i reccomend you to see the whole page , top to bottom ).

Observation ; All text outside the editor gets converted to small font size for example : "Are you posting in the right place? Check out Where should I post X? to know for sure"

the above is visible in font Verdana Regular Size 7.5 but once pressed a preview button it changes to Times New Roman 7.5 but appears in a very small font size on the screen.

Note : As a tester I am aware that this could be the problems due to my system fonts being corrupted or some application messing the font suitcase.

My PC configuration : Windows XP ( not experience ;-) , MS Office ( latest , watever with pathces ) , IE explorer 5.5 or above.

If this is not reproducible at your end , kindly excuse BUT i did check several times.

Regards

Pradeep or prad 

 I could be wrong but I am tester , mostly I am paid to be wrong to make others right

Edit by castaway - closed hanging pre tag ;)

  • Comment on Probable Bug in PM while creating a node ( preview )!

Replies are listed 'Best First'.
Re: Probable Bug in PM while creating a node ( preview )!
by Skeeve (Parson) on Oct 07, 2005 at 11:21 UTC
    Could it be that you wrote 
    <pre>
some text
<pre>

    [download]
    instead of the correct 
    <pre>
some text
</pre>

    [download]
    ?? Just wondering because <pre> is rendered into the "Comment on...." text here
    $\=~s;s*.*;q^|D9JYJ^^qq^\//\\\///^;ex;print
[reply]
[d/l]
[select]
Re: Probable Bug in PM while creating a node ( preview )!
by herveus (Prior) on Oct 07, 2005 at 14:26 UTC
    Howdy!

    The visual artifacts would appear to be browser dependent, based on my limited testing using Firefox on MacOS X 10.4. I'm suspecting that Skeeve's diagnosis is spot on.

    Nonetheless, I thought the node was worth a ++ for style and presentation. It clearly stated what was done, and what was observed, including little things like system configuration. It also showed the humility of "maybe I got this wrong", both in the title and in the body. It serves as an example of a well written report.

    yours,
    Michael
[reply]
Re: Probable Bug in PM while creating a node ( preview )!
by rnahi (Curate) on Oct 07, 2005 at 13:13 UTC
[reply]
Re: Probable Bug in PM while creating a node ( preview )!
by blazar (Canon) on Oct 07, 2005 at 11:45 UTC
    Whatever... if this is a real bug, then of course it should be fixed. However just keep in mind that you're supposed not to be using <pre> in any case...

    Indeed in my first times at the monastery I used <code> tags for actual Perl code and <pre> for other code-like stuff, like shell output. Now I just stick with <code> (or <c>) as per recommendation. I just suggest you to do the same unless you have some very good reason not to...

[reply]
[d/l]
[select]

      You can use <pre> tags when you want to show something that should stay aligned (like a ascii table or a program's output) but it is not actually code.

      The difference is that things in <code> tags are downloadable, while things in <pre> tags aren't.

[reply]
[d/l]
[select]

        No, you shouldn't. Use of <pre> tags is tolerated for very narrow content. Perhaps one day, PerlMonks will make <pre> better than HTML intended, but, for now, it is best to just never use them here.

        Don't get hung up on the word "code". It can be quite useful to download output or other things. There are more differences between 'code' and 'pre' than whether or not 'download' is offered.

        And relax and let the viewer decide whether they want to see 'download' links for just a one-line item. If you don't want to see them, then fix your settings so you don't see them anywhere rather than using the problematic <pre> tag.

        Thanks.

        - tye        

[reply]
[d/l]
[select]
      Is there a way to make <code> not show the Download link? It looks dumb when you just want to show a single-line command.
[reply]

        See Code Listing Settings, specifically, you can set the minimum number of lines before you get the link, or you can outright disable it.

        ---
        $world=~s/war/peace/g

[reply]

Back to Perl Monks Discussion