When WebKit ain't WebKit.....

[quote=109871:@Kimball Larsen]So today I’ve been working on adding a new feature in one of my apps that makes use of an HTML Viewer. The feature I’d like to add involves having section headings on the page “stick” to the top of the viewer until that section scrolls off the page, then have the next heading stick to the top of the page - similar to how the List View on an iOS app can do tricks with its headers.

At any rate, after futzing around with a few terrible jQuery-based solutions, I learned that a new standard in CSS3 is the position:sticky property, that does exactly what I need. The only problem is that it is not widely supported on most browsers. BUT - it IS supported on WebKit.[/quote]

Here is what I use to have the bar stick to the top in portrait mode at http://ios-fonts.com for the table that contains the icons :

<table style="position: fixed; text-align: left; width: 100%; top: 0px; left: 0px; background-color: rgb(235, 235, 235); height: 160px; font-family: Helvetica,Arial,sans-serif;" border="0" cellpadding="2" cellspacing="2">

No sticky.

If you open in a computer browser, you will get the bar sideways. Just resize the browser until it’s width is less than height, and it will display with the sticky bar on top. Don’t scream about the design, this is meant to be seen on an iPhone or iPad screen :wink:

That’s not what the CSS sticky position does exactly.

Here’s a video that shows you better than I could try to explain https://www.youtube.com/watch?v=utonytGKodc, and this shows us it’s probably not a good idea to use just yet http://caniuse.com/#feat=css-sticky
The video does show how to use jQuery as a workaround.

[quote=164464:@Alex Jungwirth]As i can see, there is nothing new. I also evaluated the using of Xojo and needed to stop at this point because the lack of actual HTML5-Support (for a special JS-Framework that needs a newer version).
I tried to just download the CEF3 and drop in into the libs folder. But i guess, there is more to do.[/quote]
This is more a function of the engines underlying the control
On OS X it uses the built in webkit engine

On Windows it uses either the Chromium framework (if you select webkit) OR whatever IE engine is installed
And on Windows its possible to set a very new release in “compatibility mode” that makes it run like a really old version

On Linux it will use webkit or gtkhtml (I think) as the fallback

[quote=164595:@Tim Parnell]That’s not what the CSS sticky position does exactly.

Here’s a video that shows you better than I could try to explain https://www.youtube.com/watch?v=utonytGKodc, and this shows us it’s probably not a good idea to use just yet http://caniuse.com/#feat=css-sticky
The video does show how to use jQuery as a workaround.[/quote]

Thank you for the clarification.

@ Norman
The problem with Windows is that the user may have no actual IE engine installed at all. And in this case i simply can’t deliver him the content he is waiting for when i need at least IE 10 or higher.
I can manipulate the Registry so that an App uses the latest installed IE-Version (https://o2platform.wordpress.com/2012/04/17/set-net-webbrowser-control-to-use-latest-version-of-ie/) but this fails if the user is running an old Windows XP installation.

On c# i have a few different choices (like the free GeckoFx, chromium … or some commercial ones like eo.webbrowser from essentialobjects, awesomium and others).

I felt in love with the idea to work on my mac and deliver small windows applications for the daily use but as long as there is no actual browser implemented into Xojo i simply stuck on c#.

No offense at all. I simply realized that more than 60% of internet users still uses Windows XP or Windows 7. The default browser on Windows 7 is IE8. And on Windows XP was IE 6 i think. So far far away from my requirements. I simply won’t force users to updating their Browser for my laziness :slight_smile: .

Greetings
Alex

XP is 18.93% according to Wikipedia browsing usage statistics.
Windows 7 is 55.92%, but Windows 7 browser is far more advanced than busted XP’s.

In terms of versions, netmarketshare credits IE 6 of 1.30%, 7 is 0.92%, 8 is 19.07%, 9 has 8.66%, 10 represents 5.60% and 11 is 22.26%

It is encouraging to see that old junk is relegated in the one digit category.

http://www.netmarketshare.com/browser-market-share.aspx?qprid=2&qpcustomd=0