Friday, 11 February 2011

Google Chrome is a piece of ...

Share
I switched from Firefox to Chrome some time ago, but there is one thing I really hate about Chrome. It's its complete infirmity when it comes to handling XML content.

To view and download WSDL files I have to use Internet Explorer. Why?

First, when you view WSDL in Chrome it displays an empty page, not XML tree, like for example FF or IE. And second, most terifying thing in handling XML content, Chrome is changing camel case elements' names to lowecase when you save/download XML documents. Here are examples of such elements:

<xs:complextype name="cancelBookingResponse">
    <xs:sequence>
      <xs:element name="result" type="xs:boolean" />
    </xs:sequence>
</xs:complextype>
 
<wsdl:porttype name="Warehouse">
     <wsdl:operation name="cancelBooking">
       <wsdl:input message="tns:cancelBooking" name="cancelBooking">
     </wsdl:input>
       <wsdl:output message="tns:cancelBookingResponse" name="cancelBookingResponse">
     </wsdl:output>
    </wsdl:operation>
</wsdl:porttype>

What a disgrace!

Long live IE! :)

Łukasz

20 comments:

Kris said...

Łukasz, I guess you have to try to look at it at different perspective, not everyone is a ws developer, I guess that form most of the chrome users seeing xml output incidentally would be a 'terrifying' experience instead of the opposite.
As a side note, how about using chrome build in developer tools, does the xml content there is readable?

PawełŁaciński said...

You can install XML Tree plugin (https://chrome.google.com/extensions/detail/gbammbheopgpmaagmckhpjbfgdfkpadb?hl=pl). Then you will see XML with coloured syntax. As a bonus it includes XPath navigator - when you click on an element navigator shows its XPath

P90Puma said...

You can view WSDL's in Chrome by right clicking and selecting view source.

veggen said...

Long live Opera!

Łukasz said...

Thanks guys for your comments.

I think that viewing XML documents should work out of the box, without any additional tools like in all other browsers.

And you have to agree with one thing. Changing XML content is a very bad thing. After downloading XML document using Chrome it might not validate against its schema. And this is a disgrace! Shame on you Chrome programmers!

Łukasz

Sandeep said...

For me chrome crashed too many times. May be due to installing conflicting extensions.

But Firefox detects that for me and I have all chrome features in firefox as addons

Gautam said...

Yeah I had that problem too. But view source helps.

Milan Dinic said...

Like Paweł Łaciński said, you can add the plugin for this. e.g. I expected to see rss reader add button out of box, like in ff, but that is obviously not a policy.

Anonymous said...

Hey guys - seems to work fine for me: view source and I got syntax highlighting etc. Never heard of the case problem. I ran it on this:

view-source:http://sandbox.hi5.com/hi5.wsdl

Siddique said...

I opened a bug for this about a year ago

http://code.google.com/p/chromium/issues/detail?id=35800

Not sure, why its not prioritized yet.

Kris said...

'Long live IE' ?? - Are you nuts?

Anonymous said...

Who care... Chrome is a web browser, not a XML viewer.

mario said...

It works out of the box for me. It's interpreted as text/xml, and if there is no stylesheet processing instruction, that's how it is supposed to look without any text nodes.

Nerd Progre said...

Kris said: "ve, not everyone is a ws developer, I guess that form most of the chrome users seeing xml output incidentally would be a 'terrifying' experience instead of the opposite."

Terrifying experience? Sheesh, this kind of "the user is dumb, he should know nothing about this" attitude is what caused for instance for Microsoft to hide file extensions by default in Windows...

Idiotic at best.

I wish some developers would stop thinking the end user is stupid, or should be stupid. We´re creating a generation of idiot users.

FC

Anonymous said...

Yep, chrome is stupid, what about its memory hogging, every tab is 50 mb., every .. extension is 100 mb., and you can't single thread it in ubuntu, There is a bug.
But FF is not an answer, it crashes too much.

Florian said...

You use your browser to read xml files...

Autodefaultfaillost whatever else you say.

Łukasz said...

Thanks guys for all your comments!

My post attracted a lot of attention (most probably because of its title) and I hope someone from Google come across this post and realise how "inconvenient" it may be.

More comments please :)

cheers,
Łukasz

Anonymous said...

you are fucking retarded.

Łukasz said...

wow, what an impressive comment! Don't worry, I won't remove it :)

Cayetano said...

Why don't just use an extension?

https://chrome.google.com/webstore/detail/cfphnlpadcinhoebfooghjoknlifphjb