Comments on: Microsoft, Canvas, and the WHATWG http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg Cleaning up the web with Ajax Thu, 17 May 2012 07:43:39 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: dll http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-262377 dll Thu, 27 Mar 2008 14:56:42 +0000 http://ajaxian.com/?p=2264#comment-262377 never throught about that before, great post! never throught about that before, great post!

]]> By: portraits http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-259628 portraits Tue, 04 Dec 2007 05:34:30 +0000 http://ajaxian.com/?p=2264#comment-259628 I’m pretty sure Microsoft have lots of beautiful things to say because they have released a bunch of stuff in just a short span of time. There was IE7 then Vista. But I was really wondering if there was anyone from the audience who had the courage to ask them about their quality control. Vista for instance caused a lot of computer crashes in our company. IE7 has been tagged as a copycat of Fireofx because it’s also based on tabbed-browsing. I’m pretty sure Microsoft have lots of beautiful things to say because they have released a bunch of stuff in just a short span of time. There was IE7 then Vista. But I was really wondering if there was anyone from the audience who had the courage to ask them about their quality control. Vista for instance caused a lot of computer crashes in our company. IE7 has been tagged as a copycat of Fireofx because it’s also based on tabbed-browsing.

]]> By: übersetzungen dortmund http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-259208 übersetzungen dortmund Thu, 22 Nov 2007 14:53:17 +0000 http://ajaxian.com/?p=2264#comment-259208 SVG all the way! We need interoperability, and Mozilla, Safari Leopard and Opera all support SVG... SVG all the way! We need interoperability, and Mozilla, Safari Leopard and Opera all support SVG…

]]> By: klip izle http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-258581 klip izle Sun, 11 Nov 2007 10:50:55 +0000 http://ajaxian.com/?p=2264#comment-258581 thanks good post. thanks good post.

]]> By: bahamut http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-257756 bahamut Fri, 26 Oct 2007 03:06:31 +0000 http://ajaxian.com/?p=2264#comment-257756 Provide more support for CSS and SVG. Implement Dom2 event. Provide more support for CSS and SVG. Implement Dom2 event.

]]> By: Meteko http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-257493 Meteko Sun, 21 Oct 2007 21:05:46 +0000 http://ajaxian.com/?p=2264#comment-257493 Microsoft needs more work done on improving the next IE compatibility. Get molly to do the job, i think she is the best candidate. Microsoft needs more work done on improving the next IE compatibility. Get molly to do the job, i think she is the best candidate.

]]> By: dobreprogramy http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-256604 dobreprogramy Fri, 05 Oct 2007 10:15:56 +0000 http://ajaxian.com/?p=2264#comment-256604 realy very nice article, this informations are great, thanks, very thanks realy very nice article, this informations are great, thanks, very thanks

]]> By: jewellery http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-256271 jewellery Mon, 01 Oct 2007 05:00:45 +0000 http://ajaxian.com/?p=2264#comment-256271 Why is it that Vista is one of the hottest new things out there? It brand new and not fully tested. Just like every other version of Windows that has come out, the first version is always full of bugs. I know at least 6 people that had it crash their computer because of a bug in the coding. I think I am going ot at least wait a full year before I think about moving on to Vista. Just like any of Microsofts programs. There are bound to be bugs in the system. Lets us not forget WindowsME or even WindowsXP. They were filled with problems when they came out. It took some time for them ot release a reliable version that people could work on. Just because somehting looks pretty does not mean that it is. I think that they think if they make it look pretty, it will solve everything. Why is it that Vista is one of the hottest new things out there? It brand new and not fully tested. Just like every other version of Windows that has come out, the first version is always full of bugs. I know at least 6 people that had it crash their computer because of a bug in the coding. I think I am going ot at least wait a full year before I think about moving on to Vista. Just like any of Microsofts programs. There are bound to be bugs in the system. Lets us not forget WindowsME or even WindowsXP. They were filled with problems when they came out. It took some time for them ot release a reliable version that people could work on. Just because somehting looks pretty does not mean that it is. I think that they think if they make it look pretty, it will solve everything.

]]> By: bedava ödev idnir http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-255770 bedava ödev idnir Wed, 19 Sep 2007 20:53:03 +0000 http://ajaxian.com/?p=2264#comment-255770 Kindly improve error reporting in JavaScript. Currently Firefox does a much better job of this. In IE, it is extremely hard to figure out what went wrong. Kindly improve error reporting in JavaScript. Currently Firefox does a much better job of this. In IE, it is extremely hard to figure out what went wrong.

]]> By: Kredi http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-255669 Kredi Tue, 18 Sep 2007 07:35:30 +0000 http://ajaxian.com/?p=2264#comment-255669 a firebug equivalent plugin to VS would be good, for debugging and other developer centric problems. I think so... a firebug equivalent plugin to VS would be good, for debugging and other developer centric problems.
I think so…

]]> By: baby http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-253345 baby Tue, 31 Jul 2007 02:30:21 +0000 http://ajaxian.com/?p=2264#comment-253345 I think it likely that Apple does intend to do the right thing with Canvas, it’s just that a lot of us in the open source community who see standards as a positive, look at the possibility of one of the key components in the HTML 5 being “owned” by a large corporation and shudder just a little to ourselves. In theory, those two things sound at odds -- building a web where everyone employs best practices and then forcing them to go through a company in order to achieve those practices (once when I was on a train, they turned the air up as high as it would go, and then came around selling blankets to those of us who were shivering -- same basic principle). I’m sure it will all be resolved equitably, but I’ll be a lot happier when it’s a done deal. I think it likely that Apple does intend to do the right thing with Canvas, it’s just that a lot of us in the open source community who see standards as a positive, look at the possibility of one of the key components in the HTML 5 being “owned” by a large corporation and shudder just a little to ourselves. In theory, those two things sound at odds — building a web where everyone employs best practices and then forcing them to go through a company in order to achieve those practices (once when I was on a train, they turned the air up as high as it would go, and then came around selling blankets to those of us who were shivering — same basic principle). I’m sure it will all be resolved equitably, but I’ll be a lot happier when it’s a done deal.

]]> By: Matthias http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-252307 Matthias Wed, 04 Jul 2007 14:39:52 +0000 http://ajaxian.com/?p=2264#comment-252307 For me, there is just one thing! It's all about speed! A browser is expected to do more and more in an attempt to bring fat client features to the browser. Java Syript hast to be fast For me, there is just one thing! It’s all about speed! A browser is expected to do more and more in an attempt to bring fat client features to the browser. Java Syript hast to be fast

]]> By: newkon http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-252049 newkon Wed, 27 Jun 2007 16:09:14 +0000 http://ajaxian.com/?p=2264#comment-252049 I applaud the team for embracing tabs and getting us closer to being able to write CSS and scripts without IE specific hacks, but the new interface of IE 7 was a bad idea. Why would you have the toolbar in a different place than any other Windows application? Also, every IE debugger I’ve used (and I believe I’ve used them all) tends to crash — and bring IE down with it — under certain circumstances. Usually this happens when you execute the line of code that had the null pointer, or whatever was causing the problem in the first place. I’ve done the IE team the favor of using the automated bug reporter thingy every time it happens, so wherever those messages go, they might be worth looking into. Feel free to follow up here, or send email to me via my blog or the address in the post! I applaud the team for embracing tabs and getting us closer to being able to write CSS and scripts without IE specific hacks, but the new interface of IE 7 was a bad idea. Why would you have the toolbar in a different place than any other Windows application?

Also, every IE debugger I’ve used (and I believe I’ve used them all) tends to crash — and bring IE down with it — under certain circumstances. Usually this happens when you execute the line of code that had the null pointer, or whatever was causing the problem in the first place. I’ve done the IE team the favor of using the automated bug reporter thingy every time it happens, so wherever those messages go, they might be worth looking into.

Feel free to follow up here, or send email to me via my blog or the address in the post!

]]> By: sandra http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-250319 sandra Wed, 09 May 2007 16:22:06 +0000 http://ajaxian.com/?p=2264#comment-250319 Has anyone had a problem between VWD Express and IE? I cannot get my graphics to show when view in browser. I have put them on a image button, in an image box and used them as background and IE will not show them. Help! Has anyone had a problem between VWD Express and IE? I cannot get my graphics to show when view in browser. I have put them on a image button, in an image box and used them as background and IE will not show them. Help!

]]> By: Ritesh http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-249454 Ritesh Mon, 16 Apr 2007 10:59:28 +0000 http://ajaxian.com/?p=2264#comment-249454 a firebug equivalent plugin to VS would be good, for debugging and other developer centric problems. a firebug equivalent plugin to VS would be good, for debugging and other developer centric problems.

]]> By: Mike http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-248957 Mike Mon, 02 Apr 2007 19:43:07 +0000 http://ajaxian.com/?p=2264#comment-248957 Ok, I cannot exactly say what the 'bug' is (is it even a bug?) so I will describe it. I have an element that I want to scroll if and when the content is too wide. But then I get two scrollbars, because the horizontal one (should be the only one) triggers the vertical one. I think it has to do with how/where IE places the bars (inside or outside, I can't put my finger on it). I know that Firefox and Opera behave the way I expect. Sorry if it's confusing, but I hope you will try it out and consider re-evaluating the placement of scrollbars. Ok, I cannot exactly say what the ‘bug’ is (is it even a bug?) so I will describe it. I have an element that I want to scroll if and when the content is too wide. But then I get two scrollbars, because the horizontal one (should be the only one) triggers the vertical one. I think it has to do with how/where IE places the bars (inside or outside, I can’t put my finger on it). I know that Firefox and Opera behave the way I expect.

Sorry if it’s confusing, but I hope you will try it out and consider re-evaluating the placement of scrollbars.

]]> By: Bart http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-248952 Bart Mon, 02 Apr 2007 17:54:12 +0000 http://ajaxian.com/?p=2264#comment-248952 A few other things. 1) Support for user defined events ("onFoo") 2) Support for DOMContentLoaded event (if you refuse to play nice with the rest of the world, at least come up with something equivalent). This is extremely important. As web pages rely more and more on JS and pull content that is aggregated from many sources, the body.onload is going to become more and more useless. A few other things.

1) Support for user defined events (“onFoo”)
2) Support for DOMContentLoaded event (if you refuse to play nice with the rest of the world, at least come up with something equivalent). This is extremely important. As web pages rely more and more on JS and pull content that is aggregated from many sources, the body.onload is going to become more and more useless.

]]> By: Bart http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-2#comment-248950 Bart Mon, 02 Apr 2007 17:51:02 +0000 http://ajaxian.com/?p=2264#comment-248950 1) I agree a full scale debugger would be nice, but at least provide correct line numbers/files and something more useful than "object error" 2) CSS2 compliance (including fixes to all of the old bugs that were supposedly fixed with 7.... peek-a-boo bug... still there). CSS3 things such as rounded corners would be great. 3) DOM2 compliance. Standard event model. 4) Treat html (or at least xhtml docs) as XML. Xpath on (X)HTML, ability to paste nodes across XML/XHTML, Xpath 2.0. 5) Table Layout properties 6) Native opacity instead of through filters. Any filter/Active-X/IE only that has a W3C standard that is the same thing should be ported to the standards. 7) Fix the bugs with DOM manipulation (such as pasting nodes) that cause the JS engine to follow an exponential processing time instead of a linear one (e.g. pasting 1000 table rows). 8) Native SVG/VML support. Canvas if you want, but I understand the IP concerns. Things that are open standards for years should be supported. 9) Ability to extend Element and other DOM objects. 10) Fix caching. IE6 required a minimum of 1mb cache and even with all things set to flush it, still requires holding shift for every refresh to be certain. IE7 has a minimum of 8mb cache (WHY?) and the same old issues. To be honest, IE is the main factor that is holding back the internet these days. Lack of things like SVG/VML/decent Xpath and XSLT support/poor DOM support etc while still maintaining a dominant market share means that IE is by far the lowest common denominator. Due to poor support for most anything that would truly unleash the power and potential that everyone sees coming in the internet, IE is basically an anvil in the deep end. 1) I agree a full scale debugger would be nice, but at least provide correct line numbers/files and something more useful than “object error”

2) CSS2 compliance (including fixes to all of the old bugs that were supposedly fixed with 7…. peek-a-boo bug… still there). CSS3 things such as rounded corners would be great.

3) DOM2 compliance. Standard event model.

4) Treat html (or at least xhtml docs) as XML. Xpath on (X)HTML, ability to paste nodes across XML/XHTML, Xpath 2.0.

5) Table Layout properties

6) Native opacity instead of through filters. Any filter/Active-X/IE only that has a W3C standard that is the same thing should be ported to the standards.

7) Fix the bugs with DOM manipulation (such as pasting nodes) that cause the JS engine to follow an exponential processing time instead of a linear one (e.g. pasting 1000 table rows).

8) Native SVG/VML support. Canvas if you want, but I understand the IP concerns. Things that are open standards for years should be supported.

9) Ability to extend Element and other DOM objects.

10) Fix caching. IE6 required a minimum of 1mb cache and even with all things set to flush it, still requires holding shift for every refresh to be certain. IE7 has a minimum of 8mb cache (WHY?) and the same old issues.

To be honest, IE is the main factor that is holding back the internet these days. Lack of things like SVG/VML/decent Xpath and XSLT support/poor DOM support etc while still maintaining a dominant market share means that IE is by far the lowest common denominator. Due to poor support for most anything that would truly unleash the power and potential that everyone sees coming in the internet, IE is basically an anvil in the deep end.

]]> By: Adarsh Bhat http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-1#comment-248906 Adarsh Bhat Sun, 01 Apr 2007 03:39:33 +0000 http://ajaxian.com/?p=2264#comment-248906 Kindly improve error reporting in JavaScript. Currently Firefox does a much better job of this. In IE, it is extremely hard to figure out what went wrong. Kindly improve error reporting in JavaScript. Currently Firefox does a much better job of this. In IE, it is extremely hard to figure out what went wrong.

]]> By: Rogier http://ajaxian.com/archives/microsoft-canvas-and-the-whatwg/comment-page-1#comment-248903 Rogier Sat, 31 Mar 2007 19:55:12 +0000 http://ajaxian.com/?p=2264#comment-248903 Personally, I'm not looking forward to yet another learning curve to find workarounds for a new set of problems. If you decide to improve standards support, don't be lazy and improve on everything related too. (refering to "!important" support in IE7, while still not fully supporting our beloved CSS standards, forcing us (or maybe just me?) to rely on hacks or expression-based rules to get things working) My wishlist: - follow JS/DOM/CSS/(X)HTML standards (if you really wish to invent your take on things, make them compatible with standards, e.g. mouse position, this shouldn't be hard at all) - give us proper debugging! (JS console, realtime CSS editing, DOM inspecting, watchpoints, page activity (all files downloaded, all requests and their headers/data)) - use your almighty marketing machine to make people upgrade faster (eveything you release, will be _our_ problem for at least 5 years!) Personally, I’m not looking forward to yet another learning curve to find workarounds for a new set of problems. If you decide to improve standards support, don’t be lazy and improve on everything related too.
(refering to “!important” support in IE7, while still not fully supporting our beloved CSS standards, forcing us (or maybe just me?) to rely on hacks or expression-based rules to get things working)

My wishlist:
- follow JS/DOM/CSS/(X)HTML standards (if you really wish to invent your take on things, make them compatible with standards, e.g. mouse position, this shouldn’t be hard at all)
- give us proper debugging! (JS console, realtime CSS editing, DOM inspecting, watchpoints, page activity (all files downloaded, all requests and their headers/data))
- use your almighty marketing machine to make people upgrade faster (eveything you release, will be _our_ problem for at least 5 years!)

]]>