Archive for January, 2007

The IE DevToolbar

I introduce to you, the IE DevToolbar:

Now, I hear you thinking “But, that’s no toolbar, that’s a button!”. And you’d be absolutely right. The previous versions were in the form of a toolbar, but as of beta 3, they replaced it with a far more efficient button. You won’t hear me complaining.

The IE DevToolbar is a severely overlooked, but awesome tool for debugging your pages in IE7 (and IE6). It is currently at it’s third beta, and it is steadily increasing in usefulness. I have been using it since the first beta, but this third one really gets things going.

A rundown of the functions:

  • A very capable DOM explorer
  • Very expansive source view options
  • Somewhat limited code editing options
  • Handy colour picker
  • An easy resizing option
  • A menu to validate your HTML/CSS/links/feed/508, and local HTML and CSS.
  • Also included is the option to validate in multiple ways at once
  • A ruler
  • Disable cache mode!
  • A couple more, but they aren’t of much use

The Dom Explorer


Click for large image

Without doubt, the DOM inspector is the handiest thing in the toolbar. It offers a “Select element by click” option, much like Firebug for Firefox. Once you’ve clicked on an element, you will be able to see where in the source it is located, which attributes it has, and the best, what styling is applied to it. Including the most illusive hasLayout property. Many rendering-bug are still cause by an element having no hasLayout (When hasLayout is set to -1, the element has no layout).

Source View options

The DevToolbar has 4 options to view the source: original, dom (page), dom (element) and dom (element + style). The original mode is very much like the old “view source”, with the addition of numbered rows and coloured code.

Dom (page) adds code-collapsing functions to this, which is always handy with large pages.

dom (element) views only the selected element, with only it’s parent elements. Dom (elements + style) does the same, but tells you which rules in the CSS apply to your element. In addition it also tells you on which rows it found the rules.

Code editing options

Truth be told, the code editing options in the DevToolbar are limited. So limited in fact, that the only real editing you can do is add or remove attributes and their values. Handy for checking if one of your styles are causing problems, but not for much else.

It adds an easy CSS finder, though: When you right click one of the styles (See screenshot, the style view is on the right) and select “trace style”, it will search for the specific style in your stylesheet. The view of this stylesheet is coloured and numbered like the source view options.

The Rest

These are a couple of small functions that are just handy, but don’t require much explanation:

The ruler: You can measure stuff with it. seriously.
Colour picker: Lets you pick a colour and automatically copies the hex code to the clipboard.
Easy resizing options: much like the web developer toolbar for Firefox.
Easy validation options: Again, see web developer toolbar. Added value is the ability to ping multiple validation services at once. (meaning: you can check your HTML and your CSS with one click!)
Disable cache mode: during development, keeping your cache empty saves you from a lot of headache moments. Added value is the ability to disable cache only for the current website.

Conclusion

The IE DevToolbar is a nice tool, and should be standard equipment in every web developer’s arsenal. It offers options vital for debugging render errors in IE

Also, this is my first post here, I feel the urge to introduce myself: My name is Kilian Valkhof, And I am a student/web developer. I also blog at KilianValkhof.com, about a wider variety of web-related things. Feel free to drop by and leave a comment.

Feel free to give feedback on the article, and let the rest know when you agree or disagree with things said here.

IE7 Initial Feedback - What’s Yours?

I’d like to know what everyone thinks of IE7? Can Microsoft turn it around? My initial reaction was more impressed than I thought I would be. Granted, they are few years behind the tabs and rss feed support as Apple’s Safari Browser has supported for a few years now. And they have also just introduced their own version of font smoothing. But they have been increasing their support for CSS2.0 after an outcry from the web developer/designer community. I have heard both good things and bad things from fellow co-workers, like it crashes a lot and it makes pages looks weird, I have also heard that its very slow. It took almost 60 seconds for FireFox.com to load, which I find rather ironic. Whats your feedback?

IE7 Cheat Sheet

Download your IE7 Cheat Sheet today. The cheat sheet contains commands and keyboard shortcuts for IE7.

IE7 upgrades to font smoothing…

I just downloaded IE7 on my PC box to take a test drive, as its important to my job for the sites that I worked on to be cross-browser compatible. To my surprise, IE7 is now using font smoothing, just like Apple has been doing for years. They are using a technology called Clear Type which produces a similar effect to font smoothing. It currently now works with IE7 and Outlook.

Clear Type Comparison


Link to the Microsoft Article

If you think the text is too blurry and would like to turn it off, follow these instructions:

Be default, IE7 enables ClearType font rendering in the browser. Most people, especially those with LCD screens, will notice a big improvement (if ClearType is not installed already). However, many people will not like this type of font smoothing.

    1. Open IE7
    2. Open Tool Menu
    3. Click Internet Options
    4. Click Advanced Tabs
    5. Under Multimedia, clear the Use ClearType checkbox
    6. Click OK X 2

CSS Changes to be included in IE7 Beta 2….

IE7 Beta 2 release will supposedly fix the following bugs as per the Microsoft Blog

All bugs on positioniseverything.net except the “escaping floats” bug (which is planned for the future)

Details on some of the other bugs (from sources other than the positioniseverything.net list) that we fixed:

  • Overflow now works correctly! (That means boxes do not automatically grow any more.)
  • Parser bugs: * html, _property and /**/ comment bug 
  • Select control: CSS style-able and not always on top
  • Auto-sizing of absolute positioned element with width:auto and right & left (great for 3 column layouts)
  • Addressed many relative positioning issues
  • Addressed many absolute positioned issues
  • % calculations for height/width for abs positioned elementshttp://channel9.msdn.com/ShowPost.aspx?PostID=191182
  • <?xml> prolog no longer causes quirks mode
  • HTML element truly independent of the Body (now gets its own width, height etc.)
  • 1 px dotted borders no longer render as dashed
  • Bottom margin bug on hover does not collapse margins
  • Several negative margin issues fixed
  • Recalc issues including relative positioning and/or negative margins are fixed now
  • CLSID attribute of <object> tag no longer limited to 128 characters
  • :first-letter whitespace bug described in
    http://blogs.msdn.com/ie/archive/2005/09/02/460115.aspx

    fixed
  • Descendant selector now works properly for grand children when combined with other selectors
  • First-line and first-letter now applies when there is no space between word :first-line and opening brace {
  • Pseudo-classes now are working as expected if selector is excluded
  • The :link selector works now for anchor tag with href set to bookmark
  • Addressed !important issues
  • PositionIsEverything piefecta-rigid.htm now works
  • List-item whitespace bug fixed
  • Fixed AbsolutelyBuggyII
  • Absolute positioned elements now use always correct containing block for positioning and size information
  • Nested block elements now respect all overflow declarations (hidden, scroll, etc)
  • Fixed the opposing offset problem (absolute positioned element whit all four top, bottom left and right are present)
  • <a> tags nested within LI elements will no longer add extra bottom margin when hover occurs
  • We no longer lose the image aspect ratio on refresh
  • Cleaned up our ident parsing according to CSS2.1 rules
  • Fixed parsing bugs for multi- class selectors and class selectors that are combined with id selectors
  • And many more

We also extended our existing implementations to comply with W3C specifications:

  • Enable :hover on all elements not just on <a>
  • Background-attachment: fixed works on all elements – so
    Eric Meyer’s complexspiral demo works
  • Improved <object> fallback

Conditional Comments!

IE7 isnt the worst ever, at least they have given us a way to declare specific IE stylesheets with the use of Conditional Comments. These are great little snippets of code, that allow IE to read between the comments and load a specific IE stylesheet.

Conditional Comments allow you to create a comment that only IE will read, while other browsers will simply skim over it. You can include a link to a stylesheet that declares CSS styles specifically to use with IE browsers.

Here is an example of how you can declare a stylesheet that only IE7 will see/read:
<!--[if IE 7]><link rel="stylesheet" type="text/css" href="IE7styles.css" /><![endif]-->

IE7 Reaches 100 Millions Downloads - EEEk!

Wow! Microsoft just reached 100 million downloads for their new IE7 browsers, well they are a sneaky company. They have been making the browser part of a mandatory update, so users have no choice but to download and install the browser.

IE7 - Get rid of your hacks!

After reading a recent post to the IE7 blog, Microsoft is putting the word out to everyone that they should delete hacks from their stylesheets, as updates have been made to their latest browser which fix these bugs.

From the Microsoft IE7 Blog:

We’re starting to see the first round of sites and pages breaking due to the CSS fixes we have made. We would like to ask your help in cleaning up existing CSS hacks in your pages for IE7. It is has been our policy since IE6 that under quirks doctype we will not make any behavioral changes so that existing pages will continue to render unmodified, but under the strict doctype we want to change behavior to be as compliant as possible with the web standards. For IE7, we introduced new CSS functionality (see Chris blog post for the full list) and cleaned up our parser bugs. This leads now to several CSS hacks failing. If you are using IE7 (you are MSDN subscriber or received a copy at the PDC) you may notice major sites breaking due to the use of CSS hacks and the strict doctype.

Here is a list of common CSS hacks to look out for (please also consider their variations):

IE7 Adds Web Developer Tool

Microsoft has added a Web Developer Toolset that is very similar to the infamous Web Developer Tools that Firefox has had as an extension for about 3 years now.

Welcome to IE7 CSS Help!

I have started this blog as help to all those web designers and developers with CSS and IE7. I will be updating the stylesheets for the company I work with to be compatible for IE7 and I will be documenting my progress here along with tips and tricks. Stay Tuned!