page 1 of 1
Comments: 8 | Views: 891
evildictaitor
evildictaitor
if( !succeed( try() ) ) { while(true) try(); }
The C9 frontpage is going completely AWOL on Google Chrome AND Firefox 3.0.

Seriously, go back to using tables for layout if you can't use CSS properly. It's more important that is works in all browsers than that it does fancy stuff. You still haven't fixed the editor bug in Chrome that means you can't use formatting either for that matter, or the bug that means that when you login sometimes everytime you click Reply it goes through passport login only to redirect you to the front page of that thread, ad infinitum.

 Really, Microsoft of all companies ought to be able to get such simple things right, particularly in a site dedicated to developers.
Charles
Charles
Welcome Change
I'm not seeing these problems (in any of the browsers you mention). Can you share more details of your operating system and relevant configuration?
C
Minh
Minh
WOOH! WOOH!
FF3.03, XP... Vista also broken, but not as bad


Sven Groot
Sven Groot
My name has 9 letters. Coincidence? I think not...
I see this too, Firefox 3.0.1, Vista x64.
turrican
turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein
I posted about this long ago, how the refuse to make this w3c compatible. I don't think it'll ever happen.

Smiley
Duncanma
Duncanma
Just Coding for Fun...
This really has nothing to do with testing in other browsers... well I guess it could, but it is really an aspect of the content. There was a post on the home page that put an image into the page in a strange way, which messed up the page. We test our pages in Safari, Firefox and IE ... and usually Opera as well. Chrome tends to render like Safari (for obvious reasons) so we haven't really bothered with it. I've said this over and over again, but this keeps coming up... we tend to develop in Firefox 3.x ... and then we test in IE/Safari ... so this repeated suggestion that we only test in IE has no basis in fact. Maybe you think we have to 'go live' whenever someone makes a post, but that isn't the case. No code was pushed out when this blog post was made.

It is pretty hard to imagine a programmatic way to build a website such that you could put absolutely any markup into a post and have it render right in all browsers. One way would be to severely restrict the markup that people can use, to not allow anyone to put images into their posts, etc... and we do some of that (one of the many things people complain about when we do this in the forums)... but we do allow some flexibility and count on our contributors to check that their content looks good before pushing it live. On a site like CNN or someplace similar, they would likely solve this by having all posts be text only with form fields to supply a small set of images for the article or perhaps dynamically putting images in and not allowing the author any choice in the matter. That isn't the direction we've taken for our content.

That particular issue could be fixed if we applied a max-height/max-width on images inside posts on the home page ... but it had never come up before so we had not done that yet ... we will though. Every time a piece of content, in the forums or elsewhere, finds a way to break the layout of the site, we'll try to prevent that in the future, either through CSS restrictions or html filtering of what you are allowed to enter.


Duncanma
Duncanma
Just Coding for Fun...
We don't refuse to make this w3c compatible.... we just haven't put any additional time into it. We are actually reasonably compliant compared to many public websites, although we are certainly not claiming that we are 100%.

http://validator.w3.org/check?uri=http%3A%2F%2Fchannel9.msdn.com&charset=(detect+automatically)&doctype=Inline&group=0
page 1 of 1
Comments: 8 | Views: 891
Microsoft Communities