» tagged pages
» logout

sorted by: recent | see : popular
Content Tagged with Microsoft + ie

CNET News.com, 06.07.2008: Still more reasons to avoid Internet Explorer - Defensive Computing

by Michael Horowitz: A few recent stories highlighted a bedrock of Defensive Computing - if you surf the web on a Windows computer, you are safer using Firefox as opposed to Internet Explorer.

Firefox: del.icio.us/tag/firefox

Microsoft ships another cake to Mozilla...

This one looks more delicious than the chocolate liquor cake... Probably because of the color.

Firefox: del.icio.us/tag/firefox

IE8 development: Microsoft should learn from Apple, Mozilla

MS needs to be more open exactly what standards will be supported.

Firefox: del.icio.us/tag/firefox

Is “finally” the answer to all IE6 memory leak issues?

Hedger Wang has been scanning a lot of Chinese blogs lately for solutions to IE6 and memory leak issues. One of the things he stumbled upon is a pretty nifty way of nulling the objects to stop memory leaks by using the try ... finally construct. So instead of this solution which leaks memory:

JAVASCRIPT:
  1.  
  2. function createButton() {
  3.       var obj = document.createElement("button");
  4.       obj.innerHTML = "click me";
  5.       obj.onclick = function() {
  6.         //handle onclick
  7.       }
  8.       obj.onmouseover = function() {
  9.         //handle onmouseover
  10.       }
  11.       return obj;//return a object which has memory leak problem in IE6
  12.     }
  13.     var dButton = document.getElementsById("d1").appendChild(createButton());
  14.     //skipped....
  15.  

You can use the following which doesn't:

JAVASCRIPT:
  1.  
  2. function createButton() {
  3.       var obj = document.createElement("button");
  4.       obj.innerHTML = "click me";
  5.       obj.onclick = function() {
  6.         //handle onclick
  7.       }
  8.       obj.onmouseover = function() {
  9.         //handle onmouseover
  10.       }
  11.       //this helps to fix the memory leak issue
  12.       try {
  13.         return obj;
  14.  
  15.       } finally {
  16.         obj = null;
  17.       }
  18.     }
  19.     var dButton = document.getElementsById("d1").appendChild(createButton());
  20. }
  21.  

More demos, proof of concept examples and the "finally" explanation is available on Hedger's blog: Finally, the alternative fix for IE6's memory leak is available

Ajax: Ajaxian

Windows Internet Explorer Testing Center

MSFT's setup IE8 set of tests we are using to validate our interpretation and implementation of the CSS 2.1 specification

W3C: Del.icio.us W3C Tags

Almost Precedent

thoughtful analysis of "almost standards mode" and IE 8's versioning switch

W3C: Del.icio.us W3C Tags

Jeffrey Zeldman: In defense of version targeting

Perhaps the most sensible response to the version targeting debacle I've seen so far.

W3C: Del.icio.us W3C Tags

Hixie's Natural Log: Mistakes, Sadness, Regret

Ian Hixie on the new IE8 quirks mode.

W3C: Del.icio.us W3C Tags

Mistakes, Sadness, Regret (Ian Hickson)

"I recommend not including the meta tag, or, if you are forced to include it, making sure it says 'IE=7', even once IE8 ships."

W3C: Del.icio.us W3C Tags

Quotes (Dean Edwards)

"I won't support any more cruft added to HTML without hearing the reasons. 'Don't break the Web' is a way to befuddle us."

W3C: Del.icio.us W3C Tags

End of line Internet Explorer (Mike Davies)

"Microsoft would do well to learn the lessons of Netscape and realise that Internet Explorer is functionally incapable of both preserving backwards compatibility for its half a billion clients, and supporting web standards. Something has to break."

W3C: Del.icio.us W3C Tags

isolani - Web Standards: End of line Internet Explorer

More douchebaggery from Redmond!

W3C: Del.icio.us W3C Tags

Internet Explorer Vulnerabilities in 2006 (washingtonpost.com)

wow- 284 days of vulnerabilities with ie in 2006

Firefox: del.icio.us/tag/firefox

RE: FW: IE Blog: Internet Explorer 8 and Acid2: A Milestone from Markus Mielke on 2007-12-20 (www-style@w3.org from December 2007)

I do not think I am disclosing too much by saying that HasLayout will be history with IE8 (it was an internal data-structure to begin with and should have never been exposed).

W3C: Del.icio.us W3C Tags

IEBlog : Internet Explorer 8 and Acid2: A Milestone

People sometimes ask me 'why' with regards Firefox. This is why. Without it who knows how bad IE would have been/become.

Firefox: del.icio.us/tag/firefox

W3C CSS Grid Positioning

Dimitri Glazkov has made a prediction that we will see CSS Grid Positioning in IE 8. This would make a lot of sense due to the fact that:

  • Alex Mogilevsky, and Markus Mielke, of Microsoft wrote the spec
  • If Microsoft comes out with a browser that goes above and beyond, they will be able to get rid of the monkey on their back
  • CSS grids are painful right now!

This module allows you to create a layout like this:

with:

CSS:
  1.  
  2. body { columns:3; column-gap:0.5in; }
  3. img { float:page top right; width:3gr; }
  4.  

It can be seen as a grid with 6 vertical lines and 2 horizontal lines.

We can use the grid lines to position the floating image

The statement "float:page top right" here positions the image at the top right corner of the page (as defined in [CSS3GCPM])

"width:3gr" makes image 3 "grid units" wide, where a "grid unit" is the distance between two adjacent grid lines. Each boundary between a column and a gap automatically produces a grid line, therefore to specify "two columns, including the gap between columns, but not including any gaps outside the columns" we can just say "3gr".

You will see more detailed examples, with lots of gr's (grid units).

Ajax: Ajaxian

Page 1 | Next >>