| Author |
Message |
| Registered: March 13, 2007 |  Posts: 51 |
| | Posted: | | | | @Ken Cole:
It would be nice if you make sure that the new formatting functions bold and italic results in valid html. E.g. marking a textpart and format it bold and italic results in "<b><i>Example</b></i>" which is not valid html, but "<b><i>Example</i></b>" is. | | | Never argue with an idiot. He brings you down to his level, then beats you with experience.
Wir gegen die Gier - Joseph Weizenbaum (1923 - 2008):
Nichts wird unsere Kinder und Kindeskinder vor einer irdischen Hölle retten.
Es sei denn: Wir organisieren den Widerstand gegen die Gier des globalen Kapitalismus. |
|
| Registered: March 13, 2007 | Reputation:  | | Posts: 2,005 |
| |
| Registered: March 13, 2007 | | Reputation: |  Posts: 3,436 |
| | Posted: | | | | I have also see some weird behavior about the placement of the tags (it's seems impossible to pace them around words only if they are near a line break) and, a little worse, when there is tags at the end of the Overview the closing tags gets dropped. | | | Achim [諾亞信； Ya-Shin//Nuo], a German in Taiwan.
Registered: May 29, 2000 (at InterVocative) |
|
| Registered: March 14, 2007 | Reputation:  | | Posts: 1,029 |
| | Posted: | | | | Quoting rincewind: Quote:
E.g. marking a textpart and format it bold and italic results in "<b><i>Example</b></i>" which is not valid html, but "<b><i>Example</i></b>" is. Both are valid HTML, but only the latter is valid XHTML. Quoting ya_shin: Quote:
I have also see some weird behavior about the placement of the tags (it's seems impossible to pace them around words only if they are near a line break) and, a little worse, when there is tags at the end of the Overview the closing tags gets dropped. Yep, I can confirm this. As a workaround, I always use Notepad to edit the overview, manually typing the <b> and <i> tags. I even have a custom HTML window for the Overview, which allows me to quickly copy the text with tags to the clipboard. It also allows me to easily switch between formatted, unformatted and "show tags" view. If there is interest, I can post it in the Layouts forum. | | | | Matthias |
|
| Registered: March 14, 2007 | Reputation:  | | Posts: 6,744 |
| |
| Registered: May 19, 2007 | | Reputation: |  Posts: 5,917 |
| | Posted: | | | | DJ's correct. You should never break your nesting order. |
|
| Registered: March 13, 2007 | | Posts: 51 |
| | Posted: | | | | Quoting ya_shin: Quote:
I have also see some weird behavior about the placement of the tags (it's seems impossible to pace them around words only if they are near a line break) and, a little worse, when there is tags at the end of the Overview the closing tags gets dropped. That's another point. I noticed this as I want to correct some overviews with bold text at the end. This is really nasty. | | | Never argue with an idiot. He brings you down to his level, then beats you with experience.
Wir gegen die Gier - Joseph Weizenbaum (1923 - 2008):
Nichts wird unsere Kinder und Kindeskinder vor einer irdischen Hölle retten.
Es sei denn: Wir organisieren den Widerstand gegen die Gier des globalen Kapitalismus. |
|
| Registered: March 13, 2007 | | Posts: 2,759 |
| | Posted: | | | | Quoting Dr. Killpatient: Quote:
DJ's correct. You should never break your nesting order. Yes, as written in the HTLML 3.2 specification which has been the first official specification by the W3C: Quote:
Text level elements must be properly nested - the following is in error:
This has some <B>bold and <I></B>italic text</I>. |
|
| Registered: March 14, 2007 | | Reputation: | | Posts: 1,029 |
| | Posted: | | | | Quoting RHo: Quote:
Yes, as written in the HTLML 3.2 specification which has been the first official specification by the W3C Ah, thanks. Somehow I remembered that as a "should", not a "must" clause, with the later XHTML being the turning point. | | | | Matthias |
|
| Registered: March 13, 2007 | | Posts: 51 |
| | Posted: | | | | If it is "should" or "must", it would be nice if this behaviour would be fixed in an upcoming version. | | | Never argue with an idiot. He brings you down to his level, then beats you with experience.
Wir gegen die Gier - Joseph Weizenbaum (1923 - 2008):
Nichts wird unsere Kinder und Kindeskinder vor einer irdischen Hölle retten.
Es sei denn: Wir organisieren den Widerstand gegen die Gier des globalen Kapitalismus. |
|
| Registered: March 13, 2007 | | Posts: 2,759 |
| | Posted: | | | | Quoting goodguy: Quote:
Quoting RHo:
Quote:
Yes, as written in the HTLML 3.2 specification which has been the first official specification by the W3C
Ah, thanks. Somehow I remembered that as a "should", not a "must" clause, with the later XHTML being the turning point. Even if it was a 'should' clause, it would mean in the context of those specifications that a server has to produce the correct code, while a client has to deal with incorrect code as well. This is common RFC speech (even though HTML 3.2 is not an official RFC). |
|
| Registered: May 19, 2007 | | Reputation: | | Posts: 5,917 |
| | Posted: | | | | I personally wish that browser would quit catering to the stupid so that programmers and professional web developers such as Ken can see these kind of issues quickly.
It started with Microsoft and IE because they wanted pages that looked fine with sloppy HTML in their browser to look like crap in other browsers that followed standards. Didn't help that Frontpage generated sloppy HTML. But of course, other browsers won't do that because it could hurt their market share. |
|
| Registered: March 13, 2007 | | Posts: 2,759 |
| | Posted: | | | | Quoting Dr. Killpatient: Quote:
I personally wish that browser would quit catering to the stupid so that programmers and professional web developers such as Ken can see these kind of issues quickly.
It started with Microsoft and IE because they wanted pages that looked fine with sloppy HTML in their browser to look like crap in other browsers that followed standards. Didn't help that Frontpage generated sloppy HTML. But of course, other browsers won't do that because it could hurt their market share. Trust me, this issue is older than IE. It has always been the concept of HTML that servers should strictly following the rules while clients should be tolerant what they accept. |
|
| Registered: March 10, 2007 | | Posts: 4,282 |
| | Posted: | | | | Added to the fix list for 3.6 (both issues) | | | | Invelos Software, Inc. Representative | | | | Last edited: by Ken Cole |
|
| Registered: March 13, 2007 | | Posts: 51 |
| | Posted: | | | | THX  | | | Never argue with an idiot. He brings you down to his level, then beats you with experience.
Wir gegen die Gier - Joseph Weizenbaum (1923 - 2008):
Nichts wird unsere Kinder und Kindeskinder vor einer irdischen Hölle retten.
Es sei denn: Wir organisieren den Widerstand gegen die Gier des globalen Kapitalismus. |
|
| Registered: March 14, 2007 |  Posts: 630 |
| | Posted: | | | | Quoting RHo: Quote:
Quoting Dr. Killpatient:
Trust me, this issue is older than IE. It has always been the concept of HTML that servers should strictly following the rules while clients should be tolerant what they accept. Precisely - An interesting quote on IE from Wikipedia's article on the browser war: Quote:
... it adopted the W3C's published specifications more faithfully than Netscape Navigator 4.0.
Unfortunately after IE won the browser war two things happened: 1) MS put limited development into it 2) A lot of enterprise applications where build based on IE. No matter what happens on the internet with regards to standards, Microsoft simply can't affort to break the enterprise applications. Sure they can give them a small nodge now and then, but that is it. No matter how big MS is, when the worlds largest companies line up and say "we do NOT want to invest in upgrading our infrastucture, you better make sure everything still works" even Microsoft simply isn't powerfull enough to win that battle. | | | Regards
Lars |
|