> > > #1096
> > > I included a list of names on a webpage the other day and my
> > > co-editor doesn't like to see name split across a line. I agree: when
> > > lines are long a split name looks silly when you can easily place a
> > > non-breaking space between forename and surname. Browsers kno
On 4 May 2013 John Harrison wrote:
>>> Browsers know not to split a line at
>>> a non-breaking space, don't they? Except Netsurf?
>> Yes it's a long-standing bug.
> I assume 'long standing' only relates to 3.x. 2.9 behaves correctly.
I first reported it on 25th March 2006 (1458451 still open
> > Browsers know not to split a line at
> > a non-breaking space, don't they? Except Netsurf?
> Yes it's a long-standing bug.
I assume 'long standing' only relates to 3.x. 2.9 behaves correctly.
--
John Harrison
Website http://jaharrison.me.uk
On 4 May 2013 Tim Hill wrote:
> Browsers know not to split a line at
> a non-breaking space, don't they? Except Netsurf?
> I have not reported this as a bug (yet) because I expect a crescendo of
> "we know"!
Yes it's a long-standing bug. NS will break a line at any escaped
character, tag or n
In article <534696f6bcbbai...@argonet.co.uk>, Brian Bailey
wrote:
> > #1096
> > I included a list of names on a webpage the other day and my
> > co-editor doesn't like to see name split across a line. I agree: when
> > lines are long a split name looks silly when you can easily place a
> > non-
> #1096
> I included a list of names on a webpage the other day and my co-editor
> doesn't like to see name split across a line. I agree: when lines are
> long a split name looks silly when you can easily place a non-breaking
> space between forename and surname. Browsers know not to split a lin
#1096
I included a list of names on a webpage the other day and my co-editor
doesn't like to see name split across a line. I agree: when lines are
long a split name looks silly when you can easily place a non-breaking
space between forename and surname. Browsers know not to split a line at
a non-
