Web Design. Web Production.
Even the most sceptical frontend developers will have cracked a small grin when they frist dropped their web pages into IE7 and discovered less breakage than in previous versions of IE. It seems Microsoft have finally ironed out many of their most defeating and irksome bugs and this will one day mean simpler, quicker and more cost effective CSS development. Fantastic. Thank you very much Microsoft, blah, blah, blah.
But even with these bug fixes, IE7 is still lagging behind it’s competitors, namely Firefox, Opera, and Safari, and there’s an growing call for more to be done.
Mark Nyman asks “IE7 - is catching up good enough?“, while Roger Johansson says that “IE7 is better but still lagging” and “is not ready for release”. More worryingly, there’s also a growing list of new bugs which, quite honestly, are starting to make me wonder if IE6 is not the more appealing browser of the two. Vanishing content!? Incorrect rendering!? Problems with background images disappearing or not resizing on zoom? Not good. (see IE7: Old Bugs For New for more on that).
Obviously new bugs will crop up with a new release, but Chris Wilson, the group program manager of the Internet Explorer Platform at Microsoft, and his team seem to have created a new catalogue of issues more severe than the bugs they set out to fix in the first place.
I think part of the problem comes from trying to rework a rendering engine that should have been laid to rest 5 years ago. IE7, as much as I want to love it, really does feel like a rust bucket with a new lick of paint. Shame. No thank you Microsoft, blah, blah, blah.
The good news is that Chris mentioned in his presentation at @media2006 that his return to the IE project was on the understanding that there would be more than just a one-off improvement to IE7. IE7 should be the first in a line of regular updates and enhancements designed to bring Internet Explorer (back) up to speed. Firefox has done well with this philosophy; it has a continuously evolving, modern rendering engine that is capable of meeting today’s needs. So lets hope that Microsoft follow suit with plans to introduce a new rendering engine as a priority, and that IE will oneday be the browser that we all desperately want it to be.
If someone was to say “quick - recommend me 5 Firefox extensions that you depend on to do your job” what would be in your list? Here’s mine…
(Doh! So many to choose from - maybe I should have said list 10.)
The hREsume Team over at Spur have recently released hresume Creator, an online form that will convert your resume data into HTML code that you can copy-n-paste into a web page you have control over.
The hResume creator also includes a ping notification service that allows you to notify any number of hResume Ping services whenever you have updated your resume on your site.
The hREsume Team are also responsible for the hResume plugin for Wordpress which creates a new page in your Wordpress blog specifically designed to present your resume in a visual form that is viewable by both people and computers.
Both the plug-in and the hResume Creator automatically embed semantic markup as specified in the hResume Microformat, making resumes more easily available to computers operated by employers and employment websites.
Elsewhere in the world of hResume, David Janes has updated his Almost Universal Microformats Parser with support for hResume. There’s also currently a breakout discussion concerning the “contact info” portion of the hResume schema occuring.
Yahoo! has just aquired jumpcut
Jumpcut is a video site, but the coolness is their web-based online video editor. With an easy to understand Flash interface you can rearrange and trim clips and add snazzy transitions. Also cool: you can email video from the video camera on your mobile phone to the site. Every video has a “remix” button, that when clicked makes the video you’re watching editable and mixable with your own content or other content on the site.”
source: nate koechley
Thought this might inspire anyone currently building their own web application!
I stumbled into a problem a few months back where my print style sheets were being ignored by Firefox (shock! horror!).
After a bit of investigation it seemed that print was generally a weak point for Firefox, so I chalked up my problem as one of Firefox’s rare failings.
But now, thanks to a tip off in [css-d], I’ve discovered the real reason behind the problem, namely the title attribute in the <link /> tag. This attribute doesn’t have ’side effects’ when used in other elements, but in <link /> tags for external style sheets it appears too when really it is just handled differently.
It’s all to do with persistent, preferred and alternate stylesheets. To learn why it’s handled differently, and why the result varies from browser to browser, please read: “Correctly Using Titles With External Stylesheets“
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Quisque sed felis. Aliquam sit amet felis. Mauris semper, velit semper laoreet dictum, quam diam dictum urna, nec placerat elit nisl in quam. Etiam augue pede, molestie eget, rhoncus at, convallis ut, eros. Aliquam pharetra. Nulla in tellus eget odio sagittis blandit. Maecenas at nisl. Nullam lorem mi, eleifend a, fringilla vel, semper at, ligula. Mauris eu wisi.