Browse by Tags
All Tags »
Internet Explorer (
RSS)
In today’s post, I’m going to show an interesting technique to solve a problem and then I will tear it to pieces and explain why it is actually useless. I believe that negative results should also be published so that we can save other people from wasting time trying the same thing. So here goes… A few days ago, a post on Ajaxian proposed a new version of a somewhat old technique to implement querySelectorAll on old versions of IE, using the browser’s native CSS engine. That sounds like a great idea at first, and the hack is quite clever. The idea is to dynamically add a CSS rule to the document that has the selector that you want to evaluate, and an expression that adds the matched elements to a global array. When I read this, it reminded me...
It’s been almost 2 years now since we first shipped the Internet Explorer testing VPC’s so that you could test IE6 and at the time IE7 on the same machine. We understand the need for people to test IE6, IE7 and IE8 on the same machine, and remain committed to shipping the VPC’s! The VPC’s will remain an important component of testing your sites, because they give you a real, and accurate way of seeing how your site interacts with not just rendering, but JavaScript, and other components in the browser. But there’s a new option that will work fantastically for testing layout and rendering of pages, Expression Web SuperPreview. SuperPreview allows you to compare multiple rendering engines side by side, or even super-impose...
Several people have reported seeing errors in their logs that seem to be due to requests such as this: /ScriptResource.axd?d= [lots of junk] & t=ffffffffee24147c The important part here is the HTML-encoded “&” sequence, which stands for “&” of course. If this exact URL is sent to the server, the server won’t know what to do with the escape sequence (URLs are not supposed to be HTML-encoded on the wire) so the parameters won’t get separated as expected, potentially resulting in a server error. This bug in the toolkit is an example of that: http://ajaxcontroltoolkit.codeplex.com/WorkItem/View.aspx?WorkItemId=13134 Of course, when people see 500 errors popping up in their server logs, they immediately assume the application...
I consider myself a developer more than a designer. In fact, I’m pretty bad at web design. I know what looks nice, and I know what doesn’t work well, but I’m not so good at creating kick butt designs. So, at TechEd last year, I presented “Top 10 Mistakes Made By Web Developers” and it went over extremely well, and I was asked to do it again this year. I did it twice at TechEd EMEA in Barcelona, and was asked to do it twice this year as we filled the room the first time! Since it was an Interactive session, it’s not recorded, nor are the slides put online but I offered to share some of the sites I used both as good sites and bad sites and also share the slides! I’ll be posting the demo code from WUX310 later this week! Thanks! Read More...
I got an email today asking about the best way to go about adding the X-UA-Compatible tags on ASP.NET pages where you’ve got a master page, and may want to over ride the X-UA-Compatible tag in some content pages, but not others. After playing around with it in Visual Studio for a few minutes, I pulled together the following scenarios: Access To The Server The optimal way to do this, if you have server level access, is to add the IE=EmulateIE7 as an HTTP Response Header from the server. Then, any pages served from that server will be rendered in IE7 mode. If Internet Explorer finds the X-UA-Compatible tag in both the HTTP Response Header, and as a META tag, the META tag will win out. Thus, if you've added the IE=EmulateIE7 to the server,...
Internet Explorer 8 is a unique release in the history of Internet Explorer in more than one way, but the decision to make standards mode the default means that authors of existing sites are impacted by it, if only to set the compatibility mode to IE7. But what if your site is built using components that render out markup and script over which you have little control, such as ASP.NET WebControls? Well, if one of the controls fails in IE8 standards mode, you need to either switch to compatibility mode (ouch!) or you need the component developer to ship an updated version. During the whole IE8 development cycle, we monitored the behavior of existing controls. Most ASP.NET built-in controls have been doing just fine in IE8, or the faulty behavior...
Disclaimer: I worked on the Microsoft Ajax 4.0 template engine, so my criteria are of course heavily influenced by our own design. Templates are a data rendering method that server-side developers have enjoyed since the old days of classic ASP and PHP. The idea was quite simple (add code blocks and dynamic expressions directly into HTML markup) but it revolutionized web development, which before that relied on the opposite method (spitting HTML from CGI code). On the client-side, the browser provides two ways to generate HTML: innerHTML and the DOM API. Template rendering is of course possible, but only using a JavaScript library. To be honest, one should mention XSLT here, which is standard and widely supported but whose somewhat unusual syntax...
Here's the slide deck from my session at Web 2.0 Expo last week. I cut out a few things in order to get it to fit in the 50 minute slot they allotted me, so it's kind of short, if you're looking for full details, check out the deck from Fronteers as it has a bit more detail on things. I did add a bit about search providers to this deck, so there is a little new stuff there. It was great to be in NYC for the week, and I met a lot of great people. It was exciting to see all the people who want to see IE8 and hear their excitement about standards and the new features! I can't wait to deliver! Read More...
I installed IE8 Beta 2 and tried CTRL+F this morning and here's what I got: Finally. Quite a lot of nice things in this beta actually... Read More...
More Posts
Next page »