Showing posts with label Browsers. Show all posts
Showing posts with label Browsers. Show all posts

Wednesday, March 31, 2010

My SVG Wish Test

Shaded green textured test button
Here is a little svg file that I created for what I would hope browsers would be able to render.
The rendering to the left points to the linked svg file source.
It uses some rather simple shapes, an interesting texture, and lots of transparency.
It is a texture test for a little personal pet project I have been refining and would like it to look right across all major browsers. I created it in Inkscape then edited it down to size by hand.
There is one thing about it though. Most browsers crop it at it’s canvas edges and I can see how that would be useful, but I would prefer it to not be cropped in this instance, so I’m wondering how to do that without changing the canvas size. I want the shadow to spread past the edge of the canvas and onto the page its on.
Hmm. [Update: The image now direct links to the svg file.]

Friday, March 26, 2010

IE UA String Fun

So, after reading the IE blog post about the new UA string to be used in IE9 and the general rejection by many in the web development community I thought I would have a little fun trying out a version of the string to see who uses browser sniffing.

First, the default UA string:

Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Win64; x64; Trident/4.0; SLCC1)

For comparison, the new one one from the blog post:

Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; Trident/5.0)

And the one I thought would be fun to try:

Trident/5.0 (MSIE 9.0; Windows NT 6.1; WOW64;)

I thought I would try it on the following few websites:

  Default UA IE9 UA Trident UA
google.com Looks good Looks good Looks good
bing.com Looks good Looks good Looks good
wolframalpha.com Looks good Looks good Looks good
yahoo.com Looks good Looks good Looks good
msn.com Looks good Looks good Looks good
microsoft.com Looks good Looks good Looks good
apple.com Looks good Looks good Looks good
gmail.com Looks good Looks broken Looks broken
ymail.com Looks good Not supported,
won’t load.
Not supported,
won’t load.
hotmail.com Looks good Looks good, but can’t read emails. Looks good, but can’t read emails.
linkedin.com Looks good Looks good Looks good
facebook.com Looks good Looks good Looks good. no chat though.
youtube.com Looks good Looks good Looks good
reader.goolge.com Looks good Looks good Looks good
maps.bing.com Looks good Warning page only Warning page only
maps.google.com Looks good Looks good Looks good
maps.yahoo.com Looks good Looks good Looks good
mint.com Looks good Looks good Looks good
shkyrockett.blogspot.com Looks good Looks good Looks good

 

First I created three instances of IE8 and set the UA strings for each using UAPick to change the string and the website http://www.enhanceie.com/ua.aspx so I could tell if the string had been changed.

I then duplicated the tabs in each browser instance to see if the tabs would keep the same UA string which they did. I kept the first tabs open for reference to which string was being used, then visited the different web sites in turn to see the results.

I’m curious what other sites break with these UA strings. But the fun one would be:

Trident/5.0 (MSIE 9.0; Windows NT 6.1; WOW64; SLCC2; Made You Look!)

Friday, November 20, 2009

The Browsers

A long time ago a then young company had come up with this awesome browser a window into another world. Everyone who saw it was entranced with what they saw including things they had never dreamt to be possible.

They had developed this browser on a platform that almost everyone had and could use. Now when the platform creator found out about this new browser thing they decided it made perfect sense and that such a thing should be included as a basic part of the platform so they made their own browser.

The company who had made the first browser now had competition but the new browser wasn't as good so they didn't worry too much they just kept making theirs better.

It didn't take long for the creator of the first browser to get all puffed up thinking the browser on it's own was better than the platform it was built on and soon declared to take over the platform and make everything else on it obsolete by making it's browser the foundation of everything on the platform. Let's just make the browser the platform.

Well the platform maker didn't like that to much. This was a threat to everything they had done so they took took the step to do just what the creator of the first browser had said they would do, only to make their browser the new foundation of the platform. It would be the new browser and the new platform. Everyone could build on this new platform and could write code which could be used everywhere and there wouldn't be a threat anymore.

Soon people were using the new browser more than the first because it was now included in the platform. The creator of the old browser tried to keep up but the new one was everywhere. No one had to go look for the old one to add it anymore so it was loosing ground. The creator of the old fought back against the new taking them to court. But now the new browser was so much a part of the platform that they couldn't remove it without destroying the platform.  So the creator of the first mostly gave up, handing the code to volunteers to keep it going.

Now that this threat was gone the platform creator didn't need to keep working on their browser quite as much, it could now be a stable piece of it's platform that didn't need to change so they stopped working on it and with the lawsuit on their heads they couldn't really do anymore of what they had planned to do to move everything to be written as the browser as the platform.

So they decided to start from scratch with the platform and rewrite it with a new language that was similar to what the browser used but was written in a way that was more uniform and could work better with the platform. Who needs a browser when your platform can be what was on the other side of the browser?

But as they worked on it they just kept adding and adding to it and then delaying and delaying it. It was getting better but it was nowhere near where they needed it to be to be what the old platform.

Those volunteers by now, had been working hard on the old browser, they had it up to the level and beyond of the new one. And they started to convince many to start using theirs instead and people were using it.

While deep in trying to work out the flaws of the new platform the platform maker looked up to see that the browser they had made was starting to loose ground, and they also started to realize their new platform wasn't coming together all that smooth. So they put aside the new platform and picked back up the old one and worked to make it better, while they also did their best to fix their browser which had stagnated.

But that uniform vision of a platform based on a different all encompassing browser is still the vision, it will just take more time to slowly dish out.

The revamped platform wasn't quite what was originally envisioned but it was better than what they almost ended up with. The new browser was now somewhere along the lines of being as good as the one the volunteers had done but it still needed more work.

Then comes along a late comer huffing and puffing and screaming foul play, you can't make your platform a browser! I won't be able to play! His call goes to the courts and the courts decide the platform must provide a choice in which browser is used.

Again another new platform and a new browser from the volunteers and the platform maker. And the new platform has to conform to the new rules while the others wag their tongues and point laughing.

Now the platform maker and the volunteers were in competition neck and neck with the little guy puffing up from behind, when a slick new guy steps in and looks around, he decides to make a browser of his own; He starts by pulling together pieces of other browsers that other volunteers had created and then makes it faster than any of the competition.

The two who where fighting neck and neck over features had to stop, the new guy could over take them if they weren't careful, so they all four are now racing to see who has the best.

Then while pulling ahead the new guy gets all smug and declares that his is the best browser of them all. Hey, it's even better than the platform so why do we need a platform at all? Why don't we just make the browser the platform?

So this new guy goes off and pulls together from among the works created by more volunteers, a new platform; one made almost entirely out of his new browser and one that doesn't work with the everything built on the other platform, except for what can be viewed through a browser. Even the other browsers won't work with this new platform, everything must be the browser.

Now we end up with volunteers with a browser which relies on other platforms and a platform maker with a platform which is forbidden from integrating a browser into the platform having to compete with someone who is doing what the other two had been trying to do in the first place.

We are still in the midst of the battle, who knows what will happen. The playing field is changing and the rules are no longer fair. It's certain that something is going to happen, what I do not know. But it will be an interesting race to see what comes of it.

But should the browser be the platform?

Sunday, June 17, 2007

Safari Testdrive

Okay I decided to download Safari to add it to my testing tool belt. I'm writing this post from Safari now. It was definitely not designed for Windows. The resizing borders are missing, It feels naked like this. Eek! Give me my borders please! It also added a desktop Icon without an option to not install one. One of my pet Peeves. Off you go to hide in the Quick Launch.

One thing I noticed, that I do like, is that it seems to have some interaction with the OS, or at least other browsers. I started typing the address to get to this blog and it actually showed up in the list.

Gasp! The middle click worked! It opened a new tab! Shocking! coming from an Apple product. Okay now to test the Print Preview on my Blog. Something FireFox can't handle... Cool. It works about like Opera with Print Preview. that is good.

One of the first pages I had to try of course was the Recipe page I had been working on. And... It looks just the same in Safari as it does on Opera, FireFox, and Netscape. IE and Maxthon look a little different because of a little bit of an odd spacing issue, but I think it is cool that I don't need to change that design to get it to work is Safari.

The metallic grey interface is a little depressing. I really started to love the tan color of Windows XP Luna Blue. Vista's Black is depressing too though. I specifically went online searching for a Desktop Wallpaper with a little color in it, a few weeks ago just for that cause.

I think I will stick with IE as my choice of browser it still loads faster than any of the others and I have become comfortable with IE7. I will keep it on my tool belt though to test websites against.

Tuesday, June 12, 2007

More Browser Wars are acoming

Hmm. Apple has released a beta for their browser, Safari for Windows. I'm a little torn about it.

For one thing, in my own oppinion, Apple has never really gotten the hang of programming, quality software for Windows. I don't trust ITunes or QuickTime on PC for that reason.

But I am hopeful that if the rendering is identical on PC as it is on Mac, that I won't have to buy a Mac to test web pages for Mac. Wouldn't it be great to have "One Machine to test them all! Mhaw ha, ha, hah. Oh."

On the side of competition, I don't really know how much good it will do. It will certainly be something to watch.

On a side note to the subject, apparently hackers have, within two hours or release, come up with ways to compromise a system running Safari for Windows. It is after all only Beta.

I'm a little hesitant to download it yet. But from the screenshots I have seen, the style they are touting is; the very style I have grown so annoyed at with Itunes and QuickTime. I am one of those that don't like it when someone arbitrarily skins their application for "Cool" not taking into consideration that "I want uniform conformity to my system styling". Brushed metal simply doesn't look as good on every Theme.

You know, I think I am starting to see a trend to Apple's products of late. They are building up a reputation for high end hardware more and more... They are in the process of switching from Motorola to the more Windows friendly Intel Chipsets... Their newest Systems now run Windows Vista... They are starting to port software to Windows... They are making fun of PCs.. Wait that one doesn't quite fit.

Okay I foresee the day Microsoft will make the OS of the Mac. Apple will make applications and high end hardware, as well as their now favorite mobile hardware. Well, who realy knows, only time will tell.

Okay, enough of my opinion.

Tuesday, February 20, 2007

Interesting Browser Issues

I have run into a few interesting browser issues over the past few days.

On Sunday my Mom decided she wanted to print this Blog out so she could take it up and show my Dad. She was printing from Firefox and found that it only printed three pages, all of which were missing most of the Blog. So I launched Firefox myself and sure enough, the first page would print the Title then the second page the Table of Contents and other stuff on the left side and the third page would print the first page of the Blog body of text. So I decided to print Preview in IE where it showed up perfectly. I then tried Netscape's Browser with the same results as Firefox, which shouldn't be too surprising; since the latest Netscape Browser is just a modified version of Firefox now. Opera did a pretty good job in the Print Preview, but I have become accustomed to IE7's Shrink to fit so the extra page with almost nothing on it makes me cringe, and for some reason it was set to print the backgrounds by default. It's a simple task to turn off print backgrounds but it would have used allot of ink. What my Mom eventually ended up doing was opening the page in IE6 and printing it that way. It worked for her.

If I were to venture a guess Firefox simply doesn’t know how to handle printing IFrames properly.

Now, Ie7 isn't perfect either. I have been experiencing this rather frustrating phenomenon while looking on-line for jobs. I would go to a page of Jobs and middle click a few links, that look like Jobs I could do, to open them in separate tabs, then go to the next page and then look over the Jobs in the other Tabs. If it is a Job I am definitely not qualified for I would close the tab and continue to the next until I am through the tabs and then come back to the page with the lists of jobs and repeat the process. After doing that for a while IE7 would suddenly close all instances of IE open and play the error sound. There isn't even an error reporting dialog, it just closes.

I decided yesterday that I would trace down the problem. I noticed that it happened on opening the new tab, and it seemed to have something to do with the number of tabs opened. So I opened an IE window and clicked the New Tab button until it crashed. I counted 55 Tabs including the original tab created. Then I started over again this time I clicked the New Tab button and then Double Clicked the newly created tab to close it. Doing it this way I counted 62 Tabs, including the first tab, before it crashed. I tried several more times to make sure I could reproduce it consistently, which it did, unfortunately I don't have another Machine with Windows XP on it, to see if it is a problem with my machine, or with something that is installed or whatever.

The only ideas I have as to what the problem could be; is that there is a possibility that there is a variable not being reduced when a tab is closed so that it overflows. Or that the tabs are kept in memory until there are simply too many open and once again an overflow occurs.

Update: 21 Feb 2007 9:00PM, I finaly attached WinDBG to IE and caught the exception. It seems that it has to do with the IE Dev toolbar. It is trowing an access violation error. Interesting.