Comments We just got back from an exciting week at Adobe Max. We made a lot of announcements around HTML5 and were pleased to see the communities reaction to our intent to contribute back to jQuery and Webkit to help improve the Web.
While there are a number of areas that will drive our contributions over the next few years we think that Digital Publishing really stands out. It’s an area that is very exciting right now (especially for magazine publishers) and something that is embedded within Adobe’s DNA.
Digital Publishers face the same challenges that any other developer faces in the multi-screen world. How can I make it cost effective to target multiple devices? How do I ensure that the content is searchable and discoverable? How can I produce high fidelity content?
We believe that the separation of content, layout and formatting that is provided by HTML & CSS has a lot of potential to solve the adaptive layout & design problem. The challenge is that the language and the Browsers lack the capabilities for designers to achieve this goal today. So, this is one of the first areas that we’ll be spending our time on.
The video below shows some of the prototyping work we’re doing around Webkit to improve text wrapping and layout capabilities. The team has taken the approach of extending CSS with a few new elements utilizing the webkit- prefix so that the designer can adequately describe their intent for the content as the page is resized to simulate working across different screens. We look forward to working with the Webkit Open Source project and of course the W3C to contribute our work back in the most appropriate way. And, as always your comments are very much appreciated.
Great idea. However, your examples make the most important typographical omission of HTML even more obvious – that is the lack of hyphenation. This needs to be addressed for HTML to be viable for these uses – just look at the horrible text layout these samples produce now. This is a step in the right direction, but hyphenation is needed to make it usable (and readable).
WebKit nightly builds supports the CSS 3 hyphenate property, but Google Chrome/Chromium has disabled it for some obscure perf reason.
@Asbjørn:
­works just fine, what do you want? If you want automatic hyphenation without hints, that’s not going to work. Computers never get it 100% right.Hyphenation in this sense is not manually adding a hyphen, it’s the browser inserting hyphenations where appropriate automatically and as needed when words wrap.
So what is your proposed syntax for the new CSS properties?
I have Flash disabled and see no demo. Please stop being hypocritical — if you support the Web, support the goddam Web, and use the fallback techniques your own company is now advocating for video embedding.
Alan, the video is served from YouTube. They serve up videos in Flash & HTML5. You must have a problem with your computer.
You used the old embed snippet that only serves in an object tag. The iframe based embed code chooses one of THML5 video or flash.
cf. the bottom checkbox here http://i.imgur.com/4PdJw.png
Did you publish a draft specification document somewhere about it? Could you send it as a W3C Member Submission and/or Editor’s draft to CSS WG. The earlier, the better.
This is such a great resource you are providing. I enjoy seeing sites that understand the value of providing a prime resource for free. I really loved reading your post. Thanks!
http://www.uggs-onsale-outlet.net/
a good blog article ,We stock Argyle, Bailey, Cardy, Sheepskin, … MBT.
As a matter of fact, the question is no longer if you need a website, it is now whether you have an online strategy and if it is working for you.