Dear all – here cometh a very basic html question:
I use bookmarks to navigate inside my pages.
From the current page, say index.html, I refer to a section in a different page as follows: <a href="chapter2.html#section7">
I refer to a section in the current page like this: <a href="#section7">
And in my pages I tag these sections using this syntax:
This works beautifully in Firefox. However, in IE – and thus in the eBook – it seems that when a section in a different page is loaded, it first loads the new page from the top, and then goes to the specified bookmark. This causes a flickering effect which is rather annoying.
It looks very different in IE (6.0; 5.5 and 5.0) than in Firefox.
Try putting a litlle graphic or colorful header at the top of a page (page2.htm) and then link to a subsection of that page from some other page (<a href="page2.htm#section7"> Link text </a>. In IE the header/graphic at the top of page2.htm will flash by ever so quickly before you arrive at the subsection.
This does not happen in Firefox.
In my particular application, this is an issue. I am thinking that perhaps pages can be preloaded somehow? Or perhaps I have misunderstood the use of bookmarks?
I use plain html, and have a rather complex NAV structure with dropdows based on CSS and Java. THis part works fine, a flickering of the NAV menues upon loading a new page is OK (not disturbing nor anything to do about it).
It is just the flicjkring of the content area that is disturbing. All looks great when hopping between subsections in the same page.
THought this was inevitable, but Firefox renders these pages much nicer.
Hi Storyman - I don't know where to change the cache settings. I have tried to change settings under "tools/internet options/general tab/temporary files" (or similar - I use a Swedish version of IE) to "never" instead of auto when it comes to checking for new versions of "saved temp files" . It made no difference.
But even if it did - I'm not so sure the eBook would take notice.
Is that so? I'll post a new thread on that - hopefully Sunil will set me straight there.
But I have no ideas on how to address the flickering effect. What did you do? Did it work?
There is a bug in IE that causes a flicker in the conditions that you describe. The fix is to turn off the option to load a page on every visit. Most developers want it to reload on visit for obvious reasons.
Everything is placed inside a DIV (#wrapper) This wrapper holds #Nav and #contentwrapper. The DIV #contentwrapper also holds a div #bulktext, which contains the actual content matter. I have it set up this way to make it easy to implement a “fixed” NAV in IE using overflow-auto/hidden.
In essence <div id="wrapper">
<div id="contentwrapper"> <div id="bulktext"> Good Stuff which flickers in IE upon loading… </div> </div>
<div id="NAV"> Navigation structure </div> </div>
I already had set height: 100% for all divs. And that is the settings that gives me the “flickers” as per above.
Note: my issue is with the flickering of the content in div #bulktext when going to a subsection of a new page, not the NAV.
Any suggestion on which divs I should set a heigh to?
Interesting that you bring up scrolling vs. paging. A couple of days ago I had a chance to speak to the owner of one of the largest SEO companies around. His take is that users prefer to scroll than page. At least that is what his research shows.
One thing you might consider is a floating menu that has a list of the topics for that page, then simply link anchors to those topics. Basically, I don't want the customer to ever be confused as to what to do next or how to get where they want to go.
With any business, it is up to the individual owner of said business to ensure the success of the business. You may make more or less than any sample figures or results that might be quoted on our web sites or other publications. All business involves risk, and many businesses do not succeed. Further, Answers 2000 Limited does NOT represent that any particular individual or business is typical, or that any results or experiences achieved by any particular individual/business is necessarily typical.
Our company's websites' content (including this website's content) includes advertisements for
our own company's websites, products, and services,
and for other organization's websites, products, and services.
In the case of links to other organization's websites,
our company may receive a payment, (1) if you purchase products or services,
or (2) if you sign-up for third party offers, after following links from this website.
Unless specifically otherwise stated, information about other organization's products and services,
is based on information provided by that organization,
the product/service vendor, and/or publicly available information - and should
not be taken to mean that we have used the product/service in question.
Additionally, our company's websites contain some adverts which we are paid
to display, but whose content is not selected by us, such as Google AdSense ads. For more
detailed information, please see Advertising/Endorsements Disclosures
constitutes consent for this. For details, please see Privacy.