Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Google Chrome & DotNetNuke CompatibilityGoogle Chrome & DotNetNuke Compatibility
Previous
 
Next
New Post
9/3/2008 11:48 AM
 

I'll assume this site (DNN) is using the new FCK Provider since I am currently using Chrome to make this post and the rich text editor is working for me.

At any rate, one thing to think about is how will the world change when XHTML compliance moves from "transitional" to "strict" as the norm?  Seems to me these other browsers (Opera, Safari, Chrome) are gearing towards that day.  I'll agree that for the "here and now" most users (myself included) feel that a browser is "broken" when it doesn't work with certain sites that I'd expect it to.  I frequently change between IE and Firefox (but only ever open Safari and Opera for testing) to get the best results from certain websites.

The point they (Google, Opera, Apple) are trying to make is that the world *should* conform to the web standards and make things work the way the specifications dictate they should.  The best way to get there is currently is following the XHTML strict standards and then move forward from there.

My client's sites are a little more varied than your results above, and it may be indicative of their target audiences.  I have found roughly 75% IE (drilldown to roughly 80% IE7, 20% IE5/IE6), 20% Firefox and 5% "other".  Marketing research studies have shown that, in general, that is the case around the globe.  As I mentioned though, it really depends on your target audience.  If we ran numbers like that internally at my day job, for example, we'd have 98% IE6, 1.999% IE7, and then two people using something other than that (because they have a mac).  If we branch out to our corporate website, our numbers reflect more closely the above numbers (and have a much larger sample; ~300k users vs. 900).

So long story short, we can't be shortsighted as individuals and certainly not as a community and say that supporting Safari, Opera, Chrome, are not worth it because they will just disappear or because "most mac users have switched to Firefox".  I'll venture a guess that because Chrome is a Google application it will do very well.  Does that mean I'll use it?  Probably not.  I tend to use the tools that I feel comfortable with and those tools are primarily Microsoft.  Does that mean I should ignore it?  Defintely not.

That's my bit anyway.


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
9/3/2008 12:13 PM
 

Fooberichu wrote
 

I'll assume this site (DNN) is using the new FCK Provider since I am currently using Chrome to make this post and the rich text editor is working for me.

At any rate, one thing to think about is how will the world change when XHTML compliance moves from "transitional" to "strict" as the norm?  Seems to me these other browsers (Opera, Safari, Chrome) are gearing towards that day.  I'll agree that for the "here and now" most users (myself included) feel that a browser is "broken" when it doesn't work with certain sites that I'd expect it to.  I frequently change between IE and Firefox (but only ever open Safari and Opera for testing) to get the best results from certain websites.

The point they (Google, Opera, Apple) are trying to make is that the world *should* conform to the web standards and make things work the way the specifications dictate they should.  The best way to get there is currently is following the XHTML strict standards and then move forward from there.

My client's sites are a little more varied than your results above, and it may be indicative of their target audiences.  I have found roughly 75% IE (drilldown to roughly 80% IE7, 20% IE5/IE6), 20% Firefox and 5% "other".  Marketing research studies have shown that, in general, that is the case around the globe.  As I mentioned though, it really depends on your target audience.  If we ran numbers like that internally at my day job, for example, we'd have 98% IE6, 1.999% IE7, and then two people using something other than that (because they have a mac).  If we branch out to our corporate website, our numbers reflect more closely the above numbers (and have a much larger sample; ~300k users vs. 900).

So long story short, we can't be shortsighted as individuals and certainly not as a community and say that supporting Safari, Opera, Chrome, are not worth it because they will just disappear or because "most mac users have switched to Firefox".  I'll venture a guess that because Chrome is a Google application it will do very well.  Does that mean I'll use it?  Probably not.  I tend to use the tools that I feel comfortable with and those tools are primarily Microsoft.  Does that mean I should ignore it?  Defintely not.

That's my bit anyway.

Awesome points!


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
9/3/2008 1:57 PM
 

The DNN site is using 4.9.0 RC1, which seems to be OK. I checked a site running 4.8.0 and the FCKEditor only displays raw HTML with no toolbars. Also, I noticed when I first opened the site, I see a bar across the top of the page showing:"Mode: Edit View", when not signed in.

 
New Post
9/3/2008 2:34 PM
 

I don't have any 4.8.0 sites, but I do have some using 4.8.2 (one site), 4.8.3 (two sites), and 4.8.4 (two sites) and I don't have the same behavior as far as the "Mode: Edit View".  However, I can confirm that on those versions they are using the older FCKEditor and display only the raw html (as do Safari and Opera with the same versions).

It will be interesting to see what happens over the next little while with the official 4.9.0 release and subsequently with the 5.x releases.  Things will only get better as they have shown in the past.

On that note, I thought I'd just follow up my comment about Chrome being from Google and my thoughts that such will make it successful.  Google is quite clearly the global leader as a search engine, there is no disputing that.  They also have began offering all sorts of other services from Google Analytics (ultra powerful, nice and free), GMail, Google Calendar, etc.  At this current time everything they touch turns to gold.  It won't always be that way... there will come a point that they fall, but that time isn't now.  They have the marketing and advertisment delivery that is every company's envy and they'll be able to get a lot of people to download and run Chrome through that same powerhouse.

It should also be noted that Safari is a mac browser and that, although growing, the mac usage is still optimistically at 20% globally (some studies suggest their marketshare is more like 4-5%, others suggest more along the 8% line).  So if we are to say that only 20% of the world (optimistically) are using macs and that "most" of them probably aren't using Safari or Opera, but, as suggested, they are "probably" using Firefox.  

... I completely forgot where I was going with this so I'm just going to stop now and feel like an idiot.


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
9/4/2008 3:43 PM
 

 

It looks like an old problem resurfaces in Chrome. 


Joe Brinkman
DNN Corp.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Google Chrome & DotNetNuke CompatibilityGoogle Chrome & DotNetNuke Compatibility


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out