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...ModalPopupExtender doesnModalPopupExtender doesn't work in IE
Previous
 
Next
New Post
9/11/2008 5:50 PM
 

I made a modalpopupextender that show me a usercontrol to add something, the problem is in firefos the popup works ok, but on IE the popup doesn't show on the center.  I saw some of solutions and one of them is create a new skin_type and add <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> but the problem is I making modules and then I pakage them and I send them to other portals thats are not mine but used my modules and they don't permit change their portals.

Are there other solution to solve this problem?.

 

 
New Post
9/11/2008 6:08 PM
 

Hi John,

Unfortunately the ASP.NET Ajax Control Toolkit requires the DOCTYPE be at least XHTML 1.0 Transitional.  As such, installations that use your module will need to use skins that specify this document type.  There are a couple different ways to specify the DOCTYPE, but you'll have to do this to use the toolkit.

I haven't explored this option, but it's possible that you might be able to configure the current DOCTYPE programmatically via the DNN API for pages containing your module.

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
9/11/2008 6:41 PM
 

it is possible to switch the doctype programatically (via the skinDocType literal control in pre 5.0, and via the ActiveTab.SkinDoctype property in 5.0). However, I'm not sure your users would be too pleased if you started to dynamically change their doctype based on your module needs as you could end up making their sites look wrong i.e. incorrectly rendered.

I'd suggest that your best option is to specify it as a requirement of your module. Note: the default for new installs from 5.0 is xhtml 1.0 transitional (upgrades preserve their existing doctype), so xhtml compliance (or at least the correct doctype) will become much more prevalent over time.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...ModalPopupExtender doesnModalPopupExtender doesn't work in IE


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