Hello,
I downloaded last chrome version, and I my potential customer were not using Safari, I have not tested for this familly of browsers.
Now as downloading is on every google page we could expect th usage rate to fastly rise.
And I discovered lot of problems in my css...and some in Telerik.
Perspective of many hours testing why and where.
Kwowing in advance were are the problems would facilitate the task.
So I take this opportunity to ask for an official list of problems in Telerik controls versus main browsers.
This seems a mandatory piece of work necessary to maintain any code using intensively Telerik controls.
I understand that the person in charge of marketing will says no to this request which could be interpreted as admitting dysfonctionments.
But everybody knows that these problems are created by the 'Jurassic-Parc' way browsers are developped against standards.
Having this list will appear more as an effort of Telerik in reducing its users difficulties adapting css.
Hope this will be heard, thanks to other users to confirm any interest in the request.
Thanks
CS
I downloaded last chrome version, and I my potential customer were not using Safari, I have not tested for this familly of browsers.
Now as downloading is on every google page we could expect th usage rate to fastly rise.
And I discovered lot of problems in my css...and some in Telerik.
Perspective of many hours testing why and where.
Kwowing in advance were are the problems would facilitate the task.
So I take this opportunity to ask for an official list of problems in Telerik controls versus main browsers.
This seems a mandatory piece of work necessary to maintain any code using intensively Telerik controls.
I understand that the person in charge of marketing will says no to this request which could be interpreted as admitting dysfonctionments.
But everybody knows that these problems are created by the 'Jurassic-Parc' way browsers are developped against standards.
Having this list will appear more as an effort of Telerik in reducing its users difficulties adapting css.
Hope this will be heard, thanks to other users to confirm any interest in the request.
Thanks
CS
3 Answers, 1 is accepted
0
Hi Christian Surieux,
A separate list with browser issues will definitely be helpful for some customers.
As a vendor with excellent reputation in cross-browser support, we always strive to fix any browser compatibility issues immediately after we find them or any customer reports them. We are very proud to be a market leader in cross-browser compatibility and we ensure that everything depending on our code-base is OK. Of course there are some browser peculiarities and sometimes certain features can not be supported on specific browsers. In these cases we note that in the documentation and online demos.
Sincerely yours,
Ivo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
A separate list with browser issues will definitely be helpful for some customers.
As a vendor with excellent reputation in cross-browser support, we always strive to fix any browser compatibility issues immediately after we find them or any customer reports them. We are very proud to be a market leader in cross-browser compatibility and we ensure that everything depending on our code-base is OK. Of course there are some browser peculiarities and sometimes certain features can not be supported on specific browsers. In these cases we note that in the documentation and online demos.
Sincerely yours,
Ivo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
CSurieux
Top achievements
Rank 2
Rank 2
answered on 01 May 2009, 08:38 AM
Thanks for answer Ivo,
It looks like a good starting point.
Concerning Telerik, I know and I have clear evidence of your succesfull efforts in the cross browser area.
Quite all browsers problems are ripped fastly from your control by your dev team.
But sometime this has effects on your customer code, or ypur customer would appeciate to know where problems have been encountered for specific browsers.
So, concerning the list, I expect more a list of non respected standarts and bugs by browser and version,
I am not requesting a list of Telerik problems because for this I could open a ticket and I am 100% certain my problem will be solved.
But sometime solution is in my css and not in 'yours' and knowing of a problem would be more effiscient for all of us.
Further I would expect Telerik to struggle in international standarts comittes to force browsers builders to adopt an uniform behavior...
Best regards
CS
It looks like a good starting point.
Concerning Telerik, I know and I have clear evidence of your succesfull efforts in the cross browser area.
Quite all browsers problems are ripped fastly from your control by your dev team.
But sometime this has effects on your customer code, or ypur customer would appeciate to know where problems have been encountered for specific browsers.
So, concerning the list, I expect more a list of non respected standarts and bugs by browser and version,
I am not requesting a list of Telerik problems because for this I could open a ticket and I am 100% certain my problem will be solved.
But sometime solution is in my css and not in 'yours' and knowing of a problem would be more effiscient for all of us.
Further I would expect Telerik to struggle in international standarts comittes to force browsers builders to adopt an uniform behavior...
Best regards
CS
0
Hello Christian,
Thank you for the extra details. More info on different browser specifics and how they affect customers' code (be it Telerik related or not) will definitely be helpful for the community. We will work on providing a similar resource -- there are a lot of similar resources on the internet but another one with a bit more focus on Telerik products will be helpful.
In any case, here is a concise list of front-end-related sites and blogs (some are more general), which we usually keep an eye on -- they should be helpful for your reference:
http://ajaxian.com/
http://www.css3.info/
http://www.456bereastreet.com/
http://www.alistapart.com/
http://www.csskarma.com/
http://www.smashingmagazine.com/
http://www.webstandards.org/
http://meyerweb.com/
http://www.molly.com/
http://blogs.msdn.com/ie/default.aspx
http://accessites.org/site
http://accessify.com/news
As to to "forcing browsers builders to adopt an uniform behavior", things have been going in this direction over the past years and we are seeing more and more consistency but unfortunately there are still quite a few important differences.
Regards,
Ivo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Thank you for the extra details. More info on different browser specifics and how they affect customers' code (be it Telerik related or not) will definitely be helpful for the community. We will work on providing a similar resource -- there are a lot of similar resources on the internet but another one with a bit more focus on Telerik products will be helpful.
In any case, here is a concise list of front-end-related sites and blogs (some are more general), which we usually keep an eye on -- they should be helpful for your reference:
http://ajaxian.com/
http://www.css3.info/
http://www.456bereastreet.com/
http://www.alistapart.com/
http://www.csskarma.com/
http://www.smashingmagazine.com/
http://www.webstandards.org/
http://meyerweb.com/
http://www.molly.com/
http://blogs.msdn.com/ie/default.aspx
http://accessites.org/site
http://accessify.com/news
As to to "forcing browsers builders to adopt an uniform behavior", things have been going in this direction over the past years and we are seeing more and more consistency but unfortunately there are still quite a few important differences.
Regards,
Ivo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.