Skip to main content

The HTML Mode Syntax Checker Was Out Of Control

Most of us who compose pages and posts in HTML mode are accustomed to the annoyance of the (Page / Post) Editor HTML syntax checker.

Proper HTML syntax depends upon correctly paired HTML tags. You enter an opening tag, without a closing tag - and within seconds, the syntax checker pops up and alerts you to your mistake. You then enter a closing tag, and all is well. This might be a normal event, when formatting the page / post title.

Until this week, the syntax checker gave us a brief one or two line advice, at the top of the page. Now, we see a full screen page of random text - and in some cases, no way to continue. The error message fills the screen, and we can't see the editor window - so we can't finish what we were doing.

If the HTML mode syntax checker prevents you from continuing with your editing, and if you don't panic (and good eyesight will help, too), you can recover from this problem fairly easily.

Here, I am in the process of formatting a list. I have to copy and paste the opening tags, then the closing tags, to surround a text list. If you use a magnifying glass, you can see my problem.

Until this week, we would see a brief and relevant advice. Short and sweet (sort of sweet).

Now, a syntax checker error is rather rude. I paste the opening tags - and the syntax checker immediately pops up, and fills the screen. This gives me no way to paste the closing tags.

OMG, what do I do now?

Don't panic! Just zoom out until you can see the post editor window!!

Here is where good eyesight is a big help. Find the spot where you have text to paste, paste it, and wait, patiently.

If you paste the required closing tags, in the right spot, the syntax checker will clear the error, and you can continue.

If the problem is caused by a dropped "</div>" tag, caused by over active editing, then you use the mode toggling technique, to reset the error. You can do that without changing zoom level.

In either case, you have to remain cool. If you panic, you end up having to close the post editor, without saving - and you cannot ever update the post, as you are trying to do.

Now, it's in the hands of the Blogger Engineers. As noted below, the source of the problem has been found - and the fix for the problem is being rolled out. Rollout for everybody may take over 24 hours.

Also as noted below, if you are repeatedly oppressed by this error, you may use the "Dismiss" link at the lower right of the error message, to prevent it from repeating - while you have this post editor session open. Examine the screen prints, above, to see what "Dismiss" looks like.
(Update 11/21 8:00): After a very prompt response by Blogger Engineering, this problem has been resolved.



I've been creating the complete tag in Notepad then pasting it into the editor.
Thanks for the report. We're investigating.
Also at the bottom of that message, there's a "Dismiss" link.
Once you've clicked it once, the HTML warning messages won't reappear for the rest of your editing session.
It will help until we fix this bug.
I found the bug, we're working on pushing a fix to production.
Chuck Croll said…
Thanks, Marc!

I am guessing that the push has started - but it may be up to 48 hours before 100% complete? is fixed, should take around another 6h for the push to complete.

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: