1 Correct answer
As suspected, you're mixing old fashioned syntax with modern code.
Change this:
<br />
To this:
<br>
Change this:
<hr />
To this:
<hr>
And so on....
29
Replies
As suspected, you're mixing old fashioned syntax with modern code.
Change this:
<br />
To this:
<br>
Change this:
<hr />
To this:
<hr>
And so on....
By @Nancy OShea
To add to what you said, instead of replacing all the tags one by one, probably that simply searching for :
/>
and replacing it by :
>
should do the trick and will include IMG tag as well avoiding complex REGEX
Hi Lena - Finally I figured out that Prettier was reinserting the extra slashes whenever a document was saved! Once I disabled Prettier everythng worked OK. I didn't code them in - Prettier did that.
By @SeanKK
Well, I don't use prettier myself, but as @Jon Fritz presupposes, when saving prettier should probably look at the DOCTYPE used. What is your current DOCTYPE ?
Out of curiosity I googled the subject, and I came across this interesting old discussion about slash that we are talking about.https://github.com/prettier/prettier/issues/5246
Just regular: <html lang="en"> or <html lang="es">. Not the transitional type Jon mentioned. 🙂
By @Galeodan
It appears you are a bit confused by doctype declaration vs html tag.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
...is the old XHTML 1.0 Transitional Doctype Declaration. It is no longer used in modern sites.
<!DOCTYPE html>
...is the current HTML5 Standard Doctype Declaration and needs to be the first line of your code.
<html lang="en">
...is your site's starting html tag with a language attribute set to the "en" (English) property. Your site also needs this (not necessarily the "en" part), just after the Doctype Declaration.
The first two lines of your code should be...
<!DOCTYPE html>
<html lang="en">
...anything else could be confusing your extensions/program.
Example from W3 Schools: <img src="img_girl.jpg" alt="Girl in a jacket" width="500" height="600">. Does W3C now consider this bad practice?!
By @Galeodan
No because its NOT a self closing image tag i.e. if it were it would be: (note the additional self closing red slash Ive added below)
<img src="img_girl.jpg" alt="Girl in a jacket" width="500" height="600"/ >
Self closing tags are no longer a requirement in modern coding.
Self closing tags are no longer a requirement in modern coding.
By @osgood_
========
Self-closing tags were never in HTML5. They are leftover from X/HTML docs. Code soup is what invariably happens when converting from old doc types to modern ones without starting over.
I suppose the new Validation Service is getting stickier about proper code syntax. Either that or the code was changed since running last validation checks.
I suppose the new Validation Service is getting stickier about proper code syntax. Either that or the code was changed since running last validation checks.
By @Nancy OShea
Dont know, validating code these days is pointless as it cant keep up with what all these new frameworks throw at it. You know when your code its good to go, without the necessity for checking.
Not sure what it proves these days, most large websites, spending 1000's of pounds on development costs and top devs, will have errors/warnings, sometimes running into the high 100s
I was never ever an advocate of validation and so its proven to be correct many, many, many years later.
You know when your code its good to go, without the necessity for checking.
By @osgood_
===========
I do and you do but the majority of Dreamweaver users probably don't.
I've always said clean code is easier to work with than messy code. But sometimes you have to break rules to make browsers behave. There's a fine line between knowing which rules you can break and get away with and which one's you can't.
I think self-closing tags falls into the former category because browsers are so forgiving.
AdChoices