Social Icons

Pages

Tuesday, 9 July 2013

Post Editor Problems With Blog Owners Using Internet Explorer V8

We've been seeing a steady stream of problems being reported in Blogger Help Forum: Something Is Broken, from blog owners unable to use post editor.

The symptoms are varied, in detail.
  • Some can't get the cursor active, in the window.
  • Others can't use the Preview option.
  • Still others can't Publish.
The primary symptom, seen by many, involves yet another mysterious bX code.

In many cases, this problem has been forecast, for some time - and the blog owners should blame only themselves. Many of these blog owners are using - or trying to use - Internet Explorer V8, to maintain their blogs.

Last year, Google warned us that this time was coming.
We support the latest version of Google Chrome (which automatically updates whenever it detects that a new version of the browser is available). We support the current and previous major releases of Firefox, Internet Explorer, and Safari on a rolling basis. Each time a new version is released, we begin supporting that version and stop supporting the third most recent version.

Google stopped supporting Internet Explorer V8, in 2012.
As previously announced, Internet Explorer 10 launched on October 26, 2012, and as a result, we discontinued support for Internet Explorer 8 on November 15.

Recently, as part of an update to post editor, Blogger used code which is incompatible with Internet Explorer V8. As they continue to update Blogger, to remain compatible with newer browsers, they will continue this policy.

As time progresses, more blog owners, trying to use IE V8, will find problems with Blogger - with the problems not answered by Blogger Support. Blog owners using IE V9 or V10, in compatibility mode, will also see these problems.

If you are using Internet Explorer V8, you are way overdue for a browser upgrade. If your computer uses Windows XP, then you need to replace or update your computer. As an alternative, consider using Chrome or Firefox for all Blogger activity.

The solution, for this problem, requires your action.

>> Top

No comments:

Post a Comment