The Latin here replaced with my English.
It looks like the pagination is hard coded. I would expect to make it depend on the box size.
This displays correctly, or nearly so, only in Chrome. Firfox 3.0,
which I know doesn't have many HTML5 or CSS3 features misses the
vertical date. It puts it as styled, but across the top of the
page and on top of the first text. The comment in the HTML source
says that Firefox 3.5, which is not supported in this downrev version
of Ubuntu, doesn't support CSS Transform, which does the nice rotation
of the date string. I am going to have to figure out some alternative
way to style that string as an ordinary heading if the browser doesn't
support it before I try to use HTML5 with this style on my website.
Appearently, the author didn't want to take that into account.
A Kludge would be to put a big enough
I noticed that the
But I just fixed it, The
I just posted to my main blog on blogger.com and found it a difficult experience. I don't type well, have to backspace and reedit a good deal. The textarea editor hides embedded HTML with it is easy to clobber if you re-edit a lot. That is what happened. I was using font changes to make subheadings and when the first draft got perviewed its font settings were all wrong. I was lothe to edit the raw HTML because it is so ugly, but later was glad that feature was there. Once I examined the HTML I found that it was just <span> elements with relative font resizings. These had gotten all out of whack because the closing tags had become improperly nested and an effort to fix that resulted in errors due to unmatched tags. Once I was able to fix that, the page displayed more or less as I intended. I had to be careful because the posting was long and I didn't want to lose it.
So, a couple of months ago Google had removed an option to be able to edit HTML in Documents. This caused an uproar in the support forum as several people claimed that they use the feature. In light of what just happened to me on Blogger, I wonder if Google has changed the policy.
I just noticed that when the first page of this displays the link for "more", or the next page appears at the bottom of the page and the box with all its nice 3-d effects closes at the bottom of the page below it, in Chrome. I would think that I could chunkify the display further by hardcoding the pagination with more IDs, like "page1", "page2", etc. When I type more here, I will try that. I should allow me to navigate around the page if one of those is a top link, but without a visible anchor. This is nothing new, but it is worth exploring for its utility, given the pretty layout.
I altered the behavior by removing the style for the <div> with no ID that does a display: none;. That keeps all of the divisions visible in one box, but it corrects navigation problems, for example, the "top" pointer would put you at the bottom of the first box, instead of at the top.
Now, I have added a third page to give more navigation and created a new division to control it. That did work, but they really aren't pages, not in the sense that the 3-D box uses them
I need to go look and see if the taging of elements has bee depreciated so far as CSS5 is concerned, or it hasn't yet been working. I couldn't get other subheadings <h2> to escape from the rule I made for the top one by giving it an id or class. They all stopped getting the margin-top I wanted to deal with down-rev browsers that can't transform the date string into its vertical position.
There are two ad-hoc elements in this a