WeBuilder 2011 Beta3: Didn't highlight typo in element tag

[mapleleaf]

After, spending a considerable amount of time(4hrs.) troubleshooting an error, I got somewhat upset as WB2011 should have picked up these errors BUT it didn't.

Generally when there is a syntax, typo, with respect to elements(tags) the WB 2011 will pick it up in "red" which it does BUT in this case it did not.

elements have be closed properly otherwise there will be rendering issues.

The error was as follows and WAS and is reproducible.

<article style="line-height:285px"> </article

which was to give a vertical space of 285px in the html5 document.
that followed by

<article style="line-height:285px"> </article
<a style="margin-left:-30px" class="button" href="javascript:loadwindow('tipperRD.html','820','730')" title=" Information ">
 &nsp;Tip/Info  
</a>

What was more peculiar was that the terminating </a> in the following line was highlighted in red when the whole of the line was syntactically correct.
Therefore, this is what I would term best as being an additive error than a multiplicative error as this one error created another which in this case is a false positive.

To correct the error state which took alot of time the terminating > was added to the line on which it was missing.

<article style="line-height:285px"> </article>

Ok, so what next? Is this an isolated case or does this occur with other elements?
It seems that this error is further indicated with other elements.

This type of error was also indicated when using the section element.

<section>
.
.
.
.
<section

That did not generate an error both section text were highlighted as green and not red.

I truly recommend that this be checked otherwise there will be a tsunami of problems arising when doing html5 coding.

Too bad one is unable to color the text in this section of the forum otherwise it could be more easily shown!!

[mapleleaf]

@Gatis

How wrong can you be in stating that it is not a bug.

Perhaps you are not concerned about validation. Your mind-set IMHO needs adjusting.

<section>........<section This is a most definitively bug in/with WB 2011 since it does not indicate that this is an error when in fact it is.

before ; The page validates as html5. namely <section>....<section>

when changing to <section>....<section not only does the html5 document fail to display correctly as it is intended but it also fails html5 validation

Thus, as a result, further/additional errors are indicated This error generates additional errors and it is clear that this 'syntax error' is the root cause. In other words it is a "multiplicative error". This "syntax error" should have been picked up by WB and failing to do so is a bug.


Why?
The error in not having a closing attribute for the section precipitates additional errors which collectively can be termed an additive error which generally are corrected when the first error that causes the 'cascading event' .

I fail to understand why in this forum one is unable to use the quote, color and even post images to provide proof.
Can you provide an explanation as to why?

[Gatis]

I fail to understand why in this forum one is unable to use the quote, color and even post images to provide proof. Can you provide an explanation as to why?

I can speak only for myself, as I do not know why this was made so initially, but I guess it is connected with spamming and keeping the traffic low. But I will inquire about it, and we will see if we change our mind.

Thus, as a result, further/additional errors are indicated This error generates additional errors and it is clear that this 'syntax error' is the root cause. In other words it is a "multiplicative error". This "syntax error" should have been picked up by WB and failing to do so is a bug.

As I said, this works the same as it did in version 2010. I will add this to our to do list for consideration. If a solution is possible, we will try to improve the functionality in future. We will not delay version only because the problem you reported happened on a HTML tag added in HTML5. Why should we?

I am however convinced that 'Pandora's Box' has been opened with WB 2011 and it's claim to support html5.

We are open to suggestions for improvements. This has always been so. One is sure - we will not release unstable version, otherwise, I do not see any real justification for your claim.

Gatis

[Gatis]

Thus, as a result, further/additional errors are indicated This error generates additional errors and it is clear that this 'syntax error' is the root cause. In other words it is a "multiplicative error". This "syntax error" should have been picked up by WB and failing to do so is a bug.

After investigating the problem closer, I think it can not be considered as a "multiplicative error". If you have syntax highlighter set up so that you can see HTML tags well, you will see that in the following code:

Code: Select all

<article > </article
<a style="margin-left:-30px">
aaaa
</a>

the tag "a" is not highlighted as a tag. because tag "article" is not closed. As a result, you see (red highlighting) that </a> has no corresponding opening tag.
I might be wrong, but this part of syntax highlighter for HTML has not changed for ages in our editor. And I think we won't be changing it any time soon. (Also in Notepad++ you will see the same highlighting for tag "a" from the example above).

[mapleleaf]

@Gatis

That said, I have created two pages one which will have the correct syntax that is the elements are highlighted green.
(ie) <section>..</section>

The other where both are highlighted but the element isn't the same both highlight as green
(ie) <section>..<section <<<< this is an 100% an error which generates other errors thus a multiplicative error

However, when rendering both pages there is a great difference between them
as a result of it being <section>...</section when it is to be <section>...</section>

I do agree that 2010 and 2011 are different BUT the rendering differs with html5 than it does with xhtml or html hence the fact that this was 'ok' in/with 2010 when there wasn't support for html5 whereby in 2011 there is support for 2011.

It is this to what I was referring to by stating in a previous post about the change in/of 'mindset' which wasn't any reflection of being rude despite the interpretation of others.

To prove my point, email me for the link to the two pages that clearly demonstrates this aspect that is the affect of having <section>...<section
as opposed to <section>...<section>

[chrisjlocke]

An out of sync reply from Gatis (originally in the announcements forum)

Yes, but this works the same as it did in version 2010. I do not think this can be considered as bug, although I can agree that it would be nice if it worked better.