Last modified: 2010-05-15 15:37:31 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 2390 - request for a defined "new line" after rendering
request for a defined "new line" after rendering
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.5.x
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://test.leuksman.com/index.php/Us...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-11 15:18 UTC by lɛʁi לערי ריינהארט
Modified: 2010-05-15 15:37 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description lɛʁi לערי ריינהארט 2005-06-11 15:18:39 UTC
Hallo!

a) At http://test.leuksman.com/index.php/User:Gangleri/tests/sandbox
I tried to generate "forced new lines".

Please compare with
b) [[en:User talk:Patrick#Template:Forced new line]].

Using the same syntax I did succeed at a) but failed at b).
Please explain in detail what is going on.

Please change the summary of this bug to an apropriate request about infuencing
the final rendering of the page to achieve emty lines. I think that
experimenting with a number of emty lines / counting all times again is not a
good solution.

Thanks in advance for your efforts! Best regards Reinhardt [[user:gangleri]]
Comment 1 lɛʁi לערי ריינהארט 2005-06-12 09:47:20 UTC
Hallo!

[[en:Template:Forced new line substitute]] has the following content:
{| hight={{{1}}}px
|-
| |  
|}

It seams to work at
[[en:User talk:Patrick#Template:Forced new line substitute]]
with small differences at
http://jadesukka.homelinux.org:8180/betawiki/User:Gangleri/tests/sandbox#Template:Forced_new_line_substitute

However I am neither shure if "hight" is a valid parameter as "width" because I
can see no big difference having value 1, 100 or 150.

Please let me know if this is a "valid" substitute for a defined "new line".

Best regards Reinhardt [[user:gangleri]]
Comment 2 Brion Vibber 2005-06-12 11:32:22 UTC
I really don't quite understand what this is requesting.

Can you start by explaining what you're trying to accomplish and why?
How does a "forced new line" differ from any other kind of newline, and 
where does "after rendering" come in? What's the desired outcome, and why 
would someone want to do that?
Comment 3 lɛʁi לערי ריינהארט 2005-06-12 13:43:27 UTC
In response to comment 2

The intention is to be able to generate an *empty / blank* line between
paragraphs and let *everything else* unchanged.

*everything else*
As far as I know you can insert at [[en:]] as many "<br />" as you like - the
result will be just a new paragraph. This is OK for most cases because empty /
blank lines
- at the start of a page
- before a section
- at the end of a page
- inside a section
*may* look odd.

Nevertheless there might be situations where you *want* to generate an empty /
blank  line but the impleneted / configurated "automatism" makes this
impossible. *Only* for these situations *editors* should have a solution / an
alternative to achive what *they* want.

Best regards Reinhardt

Notes:
a) At the tests links mentioned in comment 0 I experienced a different behaviour
between version 1.5alpha2 and [[en:]]. It would be *nice to know* how [[en:]]
will behave in version 1.5.
b) I did not test at [[en:]] *arbitrary* mixtures of
- <br/>
- empty lines
- lines with comments <!--- foo --->
- interwiki links
- categories
  As I understand the "automatism" should not relate to multiple <br /> only but
also on the *mixtures* mantioned above.
Comment 4 Brion Vibber 2005-06-12 14:06:15 UTC
I don't know what "automatism" is.

I see no difference between treatment of <br> between 1.4, 1.5, and the live Wikimedia 
servers. Use of <br>s between or at the end of paragraphs appears to work fine so far as I 
can see.

Additional explanation and exact details of what's wrong are required or this will be 
marked INVALID.
Comment 5 lɛʁi לערי ריינהארט 2005-06-12 15:48:01 UTC
Sorry for "automatism".

I am using the Monobook skin with Firefox.
Please see the screen dump at:
http://jadesukka.homelinux.org:8180/betawiki/Kuva:Bugzilla_2390_01.jpg

Hope this is easier to see then describe with words.

Regards Reinhardt
Comment 6 lɛʁi לערי ריינהארט 2005-06-12 17:39:31 UTC
correction for comment 1
{| height={{{1}}}px
|-
| |  
|}
Thanks Patrick!

This would help at [[en:]] but behaves different at Nuka-Wiki.

Third test at
http://test.leuksman.com/index.php/User:Gangleri/tests/sandbox#Template:Forced_new_line_substitute

Regards Reinhardt
Comment 7 lɛʁi לערי ריינהארט 2005-06-12 18:01:13 UTC
addition to comment 6
see attached screen dump
http://jadesukka.homelinux.org:8180/betawiki/Kuva:Bugzilla_2390_02.jpg
Comment 8 lɛʁi לערי ריינהארט 2005-06-12 21:34:11 UTC
Patrick suggested to use:
{| 
|-
| height={{{1}}}px | 
|}
putting height in the cell.


During last weeks I experienced different handling of empty cells in CVS.
Tables with empty cells did first show up as intended but later with broken
cells (without cell borders).

What would be safest to use in "Template:Forced new line substitute" &amp;nbsp;
or not?
{| 
|-
| height={{{1}}}px | &nbasp;
|}

Regards Reinhardt [[user:gangleri]]
Comment 9 Brion Vibber 2005-06-13 00:13:43 UTC
I have no idea what these tables and things are supposed to be about... replacing something 
that works, simply, with something very complex and unreliable? I don't think that would be 
wise.

I'm resolving this as INVALID; if anybody can figure out what this is about, please reopen 
with an explanation.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links