Hi,
This is a follow up from another thread concerning page validation and certain validation errors (NU HTML checker) that seem to be induced by the code produced by SD.
The first is caused by the video element of the element tab in SD. It creates an error about frameborder attribute being obsolete. I attach screenshot.
The last error/warning in the image about the type attribute is not induced by SD, but rather by webform builder.
The question is whether one should worry about that failure to validate? Is it something that CC should/could change for the next release? Or should one just create a personalised component with a html element?

Another thing I have been discussing on another thread with Inger is the conversion of special characters. I noticed that accented capital characters strangely do not validate (ÁÍ) even when typed directly in the CC application. The only way to remove the validation error is to take off the accent of the character or insert the Á or Í which in turn is not displayed correctly in SD.
Please refer also to our original conversation: https://www.coffeecup.com/forums/site-designer/special-characters-and-html-entities/?post_id=293229#post293229

Regards

Regarding the last sentence above, I have just added a post there.

Frank

I reply here in order to keep the topic together.

Considering that all other accented characters validate just fine, I don't think it is a matter of changing code pages.

My suggestions had in mind that the problem related to accented upper case letters, which might affect matters such as line spacing. The declaration of language (and the use of the language attribute where appropriate) seem to me possibly relevant to the matter in the light of https://www.w3.org/International/questions/qa-lang-why and some of the further reading mentioned in that page.

Frank

It is difficult for sites (like mine) that are written in english language, but have a lot of content, references and names that use extended characters from other language. There is no simple solution. The page validation for some of my pages suggests to classify them as spanish, while 99% of the content is written in plain english.

regards
Berthold

I also looked for a way to set the lang attribute for determined sections of the page, but SD does not allow for setting the lang attribute other than globally in the head section.

Since English characters don't create the problem, and Spanish ones do, might making the declaration as Spanish (as suggested by the validation site) perhaps solve the problem?

Frank

If my last post doesn't solve the problem, custom CSS files can, of course, be put in SD4 Resources, and edited there. It should therefore be easy to put as many lang attributes as one wants in SD4 by that method. https://www.w3schools.com/cssref/sel_lang.asp shows how lang attributes are put in CSS files.

Frank

The first post in this thread refers to the validation error from the inclusion of frameborder in the iframe generated by the Video Platform Element. I have made a report to the CoffeeCup team accordingly.

Frank

Thanks Frank! Those are very good suggestions! Still I think there is some hickup within the UTF-8 charset, as it does not make sense that all accented characters validate except Á and Í.
At the moment, I also serve a spanish language legal terms as modal via the footer. I realised that that probably throws off the NU validator.
What I probably will do is taking it out from the modal and put it in its own page.

Regarding the Iframes issue, I also get a lot of warnings from Insight about frames not being valid under HTML5.
I found this http://www.simplehtmlguide.com/youtube.php and will try it later.

That being said, the failure to validate is due to the frameborder attribute. So another option would be to make a custom component that does not use the frameborder attribute but rather a class.

Regards