If you look at http://boltwire.com/index.php?p=test.badbox you will
see that depending on how you do the markups, you get different
results.

The way it works, is a line return in the box means to set it as a
div. Otherwise it sets it as a span. You can see the difference in the
html.  You should only use the box tag without linebreaks when it is
indeed in a span, or part of line. Not an entire line by itself.
Otherwise you could the result you see here.

I'm not sure if it's a but or just a consequence of BoltWire doing
what you tell it to do. Changing the style would likely cause
imperfections in other situations. I haven't researched it fully. But
I do know I spent a LOT of time trying to get the line spacing to work
right and produce valid xhtml. I'm hesitant about changing things if I
can avoid it.  :)

Cheers,
Dan


On Mon, May 18, 2009 at 2:19 AM, chFaure <[email protected]> wrote:
>
> On 17 mai, 21:46, The Editor <[email protected]> wrote:
>>
>> As for the box style, could you give an example of markup that doesn't
>> display right? It seems to work right on my site, but it may be I have
>> other style rules that go with the box style to get the line spacing
>> right.
>>
>
>
> I confirm a small trouble with <box> and <code>...
> "The code
> <box>this box</box>
> is now ugly."
>
>  gave 3 lines :
> The code
> [ this box ]
> is now ugly.
>
> Since 3.04
> the box is above the text.....
>
>
> We can avoid this closing the box in an "empty line"
> The code
> <box>this box
> </box>
> is now OK...
>
> But before 3.04, it was not possible to enclose a box in the text...
> using
> I'm an <box>inserted box</box> in a sentence...
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to