Blank line in code

[Jellby]

I've noticed that whenever I use the [code] tag, a blank line (or some blank space, at least) gets added to the end of it. For instance, if I write this:

[code]Test[/code]

I get this:

Test

(which, at least in my screen, shows a frame about two text lines high, only the top one of them is occupied by the word "Test")

I wonder if this blank line comes from some internal coding or styling, and if so, can it be removed?

[GeoffC]

said a 'green one' to the other 'green ones' .....

[Billi]

This happens with me quite often that when I want to have a blank line in a post or in a PM that the system adds further line(s).

What helps is click "Preview Post", delete all the additional lines and only then click "Submit Reply".

[JSWolf]

This is a
test which didn't pass.

[netseeker]

Originally Posted by Jellby

I wonder if this blank line comes from some internal coding or styling, and if so, can it be removed?

Jellby, i've checked the generated HTML code and it seems to be a css issue. (I think it's due to a incorrectly calculated height attribute added to the <pre>-element) Send Alex a PM, i'm sure he will try to fix it.

Originally Posted by GeoffC

said a 'green one' to the other 'green ones' .....

What's bad about discussing such things in public?

[GeoffC]

[Alexander Turcic]

Testing (please ignore):

<?php
/**
 * WordPress Cron Implementation for hosts, which do not offer CRON or for which
 * the user has not setup a CRON job pointing to this file.
 *
 * The HTTP request to this file will not slow down the visitor who happens to
 * visit when the cron job is needed to run.
 *
 * @package WordPress
 */

ignore_user_abort(true);

if ( !empty($_POST) || defined('DOING_AJAX') || defined('DOING_CRON') )
        die();

/**
 * Tell WordPress we are doing the CRON task.
 *
 * @var bool
 */
define('DOING_CRON', true);

if ( !defined('ABSPATH') ) {
        /** Setup WordPress environment */
        require_once('./wp-load.php');
}

if ( false === $crons = _get_cron_array() )
        die();

$keys = array_keys( $crons );
$local_time = time();

if ( isset($keys[0]) && $keys[0] > $local_time )
        die();

foreach ($crons as $timestamp  => $cronhooks) {
        if ( $timestamp > $local_time )
                break;

        foreach ($cronhooks as $hook => $keys) {

                foreach ($keys as $k => $v) {

                        $schedule = $v['schedule'];

                        if ($schedule != false) {
                                $new_args = array($timestamp, $schedule, $hook, $v['args']);
                                call_user_func_array('wp_reschedule_event', $new_args);
                        }

                        wp_unschedule_event($timestamp, $hook, $v['args']);

                        do_action_ref_array($hook, $v['args']);
                }
        }
}

die();

[Alexander Turcic]

Fixed I believe.

It was related to some code that calculated the pixel height of the resulting code block. For some reason it always added 18 pixels to the total (i.e. the blank line at the end was meant to be a feature).

[Jellby]

Thank you!

It even fixes all code blocks already posted.

[GeoffC]

[Jellby]

And this?

“<img class="spacer" src="empty.png" alt="">‘Because,’<img class="spacer" src="empty.png" alt="">” he read.

In my screen I see it as a 1-line-high box, but with scrollbars, which make it unreadable (snapshot attached).

[pholy]

That's probably what the 18 pixels were for - whether they were needed or not!

@Jelby - Don't you know that long lines of code violate the "Coding Standard"? We are trying to help you comply...

[JSWolf]

So basically, the fix breaks things. Time to remove the fix.

[Alexander Turcic]

Originally Posted by JSWolf

So basically, the fix breaks things. Time to remove the fix.

We reverted the code, so the initial issue (one blank line at the end of the code) is present again. I guess the easiest is to live with that blank line until we decide to make a major upgrade to the forum software.

[JSWolf]

Originally Posted by Alexander Turcic

We reverted the code, so the initial issue (one blank line at the end of the code) is present again. I guess the easiest is to live with that blank line until we decide to make a major upgrade to the forum software.

Any word on proper quoting? Are we ever going to get it? I noticed in another forum I belong to that uses the same software, that you can only quote 3 or 4 levels. I think that works very well without making quotes a mess.