The disappearing scroll tab, in the latest Chrome browser version, is tres elegante - for some blog owners.
Personally, I'm not convinced.
Hover the cursor in the scroll tab area, to get the tab to pop out.
If you use the Chrome browser, and the display content is longer (or wider) than one physical screen, you may not realise that.
Some people may think that part of their blog - their post - or their template - has been lost.
But, look again.
Now, you see it.
Now, you don't.
If you use a "mouse" with a scroll wheel, this is not a problem. Start scrolling with the wheel, and the tab pops out.
For folks who are accustomed to "grabbing" the tab, and dragging it downwards (sideways) to scroll, this is not a step forwards. If you want to read text, that's above the bottom of the blog, how do you scroll left to right, while reading a long line of text?
Look at what our readers see.
Now, you see it.
Now, you don't.
Where did the rest of my main page go??
What our readers think, when using Chrome, is another question.
I think that the scroll tab is another "well enough".
Now, you see it.
Now, you don't.
Where is the rest of my post code? What the #@!!?
At any rate, if you - or your readers - think that blog, post, or template content has mysteriously vanished, try using the scroll tab (if you can find the tab). You may find the "missing" content, right in front of you.
The Chrome Engineers recently added an elegant enhancement to their browser. If you're not scrolling up and down (or right to left), you don't have to look at that nasty old scroll tab - even when using the #Blogger post editor.
I'm not convinced that this is a step forward.
Last month, as part of the SSL rollout, Blogger added a page / post / template editor feature - that not everybody understands.
A blog with "HTTPS Redirect" enabled will provide SSL access, for every reader - both those who intentionally use HTTPS, and those who normally use classic "HTTP". Those who normally use "HTTP" will find themselves redirected to "HTTPS" - no choice.
When you use page editor, post editor, or template editor, on a blog which offers "HTTPS" to everybody, you may see an alarming alert.
If you decide to enable "HTTPS Redirect" on your blog, page editor, post editor, and template editor will let you know when you are editing mixed content.
This page contains HTTP resources which may cause mixed content affecting security and user experience if blog is viewed over HTTPS.
When editing pages and posts, on a blog with "HTTPS Redirect" enabled.
Editing your template so it mixes HTTP and HTTPS may affect the security and user experience of your blog when it is viewed over HTTPS. Learn more. Hide warning
And when editing the template, on a blog with "HTTPS Redirect" enabled.
You will have several choices, when encountering the "This page contains HTTP resources ..." / "Editing your template so it mixes HTTP and HTTPS" alert.
- Change all links to "HTTPS:", using "Fix".
- Fix each link selectively, and select "Dismiss".
- Don't change anything, and select "Dismiss".
- Don't enable "HTTPS Redirect".
Change all links to "HTTPS:", using "Fix".
Select "Fix" - and page / post / template editor will automatically change every "http:" reference to "https:".
You will have broken links, which reference services and websites that do not yet support SSL. You will eventually need to find out what services and websites you link and use, that don't provide SSL - and drop them, or encourage them to upgrade.
Fix each link selectively, and select "Dismiss".
You will have broken links, which reference services and websites that do not yet support SSL. The links that you leave as "HTTP:" will still throw "Mixed Content" warnings.
Don't change anything, and select "Dismiss".
Your blog will throw "Mixed Content" warnings.
Don't enable "HTTPS Redirect".
Let your readers decide how to access the blog. The readers who use HTTPS will see "Mixed Content" warnings.
"Mixed Content" warnings will be around, for a while.
Until all blogs, services, and websites provide SSL, every blog and website that links to or uses those blogs, services, and websites is going to throw "Mixed Content" warnings.
The purpose of the warnings is to let the readers of our blogs know of possible risk.
Hey! This blog has content that may not fully support your need for security!!
That's what the warnings are designed to do. Keep our readers informed, so they can protect themselves.
Not every blog owner knows what to do, when using #Blogger page, post, or template editor, and encountering the Blogger equivalent of a "Mixed Content" alert. Blogs that have the recently added "HTTP Redirect" option enabled will be susceptible to this alert.
https://productforums.google.com/forum/#!category-topic/blogger/SHhkzy1uh8g
In the process of publishing my earlier post "Blogger Magic - Add An HTML Gadget", I discovered the latest feature in the Blogger SSL upgrade.
Page / Post Editor now scans page / post content, and warns us when there are links still using "http" protocol. This will help us avoid publishing pages and posts which will generate "Mixed Content" warnings, when pages and posts are displayed using SSL.
The new post editor tool will help us avoid subjecting our readers to unexpected "Mixed Content" warnings.
We will be responsible for finding out what specific content can be accessed, using SSL. If we believe that a significant proportion of the identified page / post content can be accessed using SSL, we can have all content automatically changed from "http" to "https" - then deal with individual access problems.
The "Fix" link will change all "http:" links to "https:".
If you believe that all links, currently accessed using "http", can be accessed using "https", you can use the "Fix" link. Otherwise, use "Dismiss", then manually change individual links.
Alternately, use a browser based "string find" tool, as available, and identify each instance of "http:".
If you change an individual link, or use the "Fix" option - and you change to "HTTPS" for a blog, service, or website that does not support SSL - that blog, service, or website reference will break. So edit carefully! Only you can decide if broken gadgets / links are better than "Mixed Content" alerts.
The "Dismiss" link lets you evaluate each "http:" link, using the browser "find" wizard.
Then, make your own decision.
Using either "Dismiss" or "Fix", you are responsible for each link - if you want your readers to get results from each link that you provide.
Click on "Learn more", for more information, in Blogger Help: Fix mixed content on your blog.
Which ever you choose, your readers benefit should be your guiding force.
As part of providing SSL connectivity for our blogs, #Blogger now provides an "http:" detector, in post editor. The blog owner has the choice to change each "http:" link in the post automatically - or to manually evaluate change each link, and change when appropriate.
Sometimes, advice provided in Blogger Help Forum: Get Help with an Issue, comes too late.
Telling people to avoid use of MS Word, for composing posts, is one example of "too late". But maybe this delinquency can be repaired.
Blogger provides the the page / post editor "Remove formatting" tool ("Tx"), for removing unwanted formatting.
When you've just published your post - and can't figure out why the formatting is all whacky - or maybe you can't get the post successfully passed through a FeedBurner feed - the most obvious way to correct the post is to use Notepad, or a similar text editor.
But that's a pain, and it's rather complicated. Maybe there's an easier solution.
Like an over edited post - or a victim of too much switching between Compose and HTML modes - the "Remove formatting" tool ("Tx") might save you, here.
Select everything in the page / post.
And use the editor "Remove formatting" tool ("Tx").
As in the previous example, you may have to spend a few hours adding essential formatting back. But with MS Word meta formatting, aren't you better off getting rid of all of that, at once?
Some #Blogger blog owners publish posts full of junk meta formatting, courtesy of MS Word - then look for a quick solution. Copying out then back, using Notepad / WordPad, or a similar text editor is the most obvious solution - but it's a painfully complicated one.
Maybe this is another case when the page / post editor "Remove formatting" tool can save the day.
We have a small but vocal group of blog owners, in Blogger Help Forum: Get Help with an Issue, who report that they are unable to use Post Editor, to upload photos.
When trying, they get an errorDo you want to open or save resumable (1.61kb) from www.blogger.com?
Right now, it appears that the problem is common to older versions of Internet Explorer.
The blog owners willing to provide details, about their browser, appear to be using Internet Explorer V8 or V9.
It is possible that the owners having a problem with IE V9 are using Blogger with Compatibility View enabled - which effectively gives them IE V8. Noting that Internet Explorer V8 is considerably out of date - and is now not supported by Blogger - it's possible that the primary cause of the problem simply involves use of IE V8 (or V9 with "Compatibility View").
We have a Problem Rollup Discussion, in Blogger Help Forum: Get Help with an Issue, where we are requesting details from everybody who is experiencing this problem.
While we wait for action by Blogger Engineering, everybody experiencing this problem is strongly urged to contribute their details to the Rollup Discussion. Problem diagnosis being as it is, any one person, contributing their details, might contribute the one essential detail that leads to successful diagnosis of the problem.
Alternately, you might consider upgrading Internet Explorer - or disabling "Compatibility View", for "blogger.com".
Some blog owners, when publishing a new page or post, really appreciate the "Preview" option in the page / post editor.
In some cases, some people may use "Preview" so instinctively, they may overlook the limitations. We see the confusion, occasionaly, in Blogger Help Forum: Get Help with an Issue.Where is my page? There's no selection, under "Pages to show", even!
The blog owner does not realise that unpublished pages or posts won't be visible, outside the page / post editor, and the "Preview" window.
In some cases, the confusion is not apparent, until we view the Pages or Posts menu - and see the "Draft" caption, next to the missing pages or posts.
If you really want to view the page or post, outside the Preview window - maybe to check the links - you have to Publish. In most cases, you can just Publish, then modify / update as you continue.
If it's so important to see the page or post - and you do not want it to be visible to your readers - setup a test blog. Then, copy or edit the page or post in the test blog - and Publish at will.
Just don't be unduly alarmed, when you look at your blog - and don't see the page or post, before you Publish.
>> Top
