I would like to use the Popup feature (window.createPopup() ), but when I
create pop-ups, the HTML and styles I pass the pop-up are interpreted in
old bugwards-compatible mode (bounding boxes interpreted incorrectly,
features such as 'white-space' not available).
I can't figure out a way to force IE6 to interpret the Pop-up doc as a
standards-compliant document--that is I can't find anyway to set the
DOCTYPE.
Is this possible, or am I stuck use old crappy-CSS in pop-ups?
Thank you for your help!
- jeff
Unfortuneatly, due to our wonderful interlectual property protection policy,
I can't give you the code we use, as it is in one of products, but if you
think it through, it's not too hard to write a good reliable system (or find
one on the many assorted JavaScript websites)
"Jeff Wishnie" <jeff> wrote...
And if someone is already using window.createPopup() in IE6 standards
compliant mode she/he surely will know about the standard window.open method
which is on several points quite different from window.open.
Cy
"Rowland Shaw" <spamf...@anotherpointless.org> schreef in bericht
news:#II9rsPzCHA.2232@TK2MSFTNGP11...
I am using popups a lot in email and then I use two methods:
Specifying the popup content and popupstyle sheet in a hidden container(DIV)
and then referencing that container as innerHTML of the popup body
A Mr. Gerard Ferrandez has found a bit strange way of getting the stylesheet
active:
// ------------------------------------------------------------
// Version OE5.5 Plein Ecran - Fullscreen
// auguste 2000 - Gerard Ferrandez
// ------------------------------------------------------------
objPopup=window.createPopup();
objPopupBody=objPopup.document.body;
Method 1:
objPopupBody.innerHTML="<div
style='display:none'>"+PopupStyle.innerHTML+"</div>"+src.innerHTML
(the PopupStyle is the id of the style element (actually style can't have an
id i think according to standard?) which is included in the 'src' hidden div
with popup content.
Method 2:
You can have the same effect by writting:
objPopupBody.innerHTML="<body>"+src.innerHTML
I havent tested it but maybe injecting the style in like that will keep it
compliant?
There is another method which might be the best possibility . The default
download behavior.
You can specify the popup content as a seperate HTML page in standard
compliants mode and then inject that normal page in your popup.
(works for web but offcoursde not for mail as both page need to be on the
same server).
If it doesn't help then you've got a wrong implementation of the popup by
microsoft. (informed them?)
Cybarber
"Jeff Wishnie" <jeff> schreef in bericht
news:Xns9318A9B7ACAED...@207.46.248.16...
> "Rowland Shaw" <spamf...@anotherpointless.org> schreef in bericht
> news:#II9rsPzCHA.2232@TK2MSFTNGP11...
> We found it easier to write our own popups for the application we
> developed, which also had the added advantage of being cross-browser
> compatible.
>
> Unfortuneatly, due to our wonderful interlectual property protection
> policy, I can't give you the code we use, as it is in one of
> products, but if you think it through, it's not too hard to write a
> good reliable system (or find one on the many assorted JavaScript
> websites)
>
>
> "Jeff Wishnie" <jeff> wrote...
>> I'm using IE6 in Standards-Compliant mode to build a DHTML/CSS
>> application.
>>
>> I would like to use the Popup feature (window.createPopup() ), but
>> when I create pop-ups, the HTML and styles I pass the pop-up are
>> interpreted in old bugwards-compatible mode (bounding boxes
>> interpreted incorrectly, features such as 'white-space' not
>> available).
>>
>> I can't figure out a way to force IE6 to interpret the Pop-up doc as
>> a standards-compliant document--that is I can't find anyway to set
>> the DOCTYPE.
>>
>> Is this possible, or am I stuck use old crappy-CSS in pop-ups?
> Why are you pretending to be so wonderfull.
> It doesn't help a bit posting answers like that. And for what its
> worth your socalled called code is probably some standard way of
> using the window open feature packed nicely for your app nothing to
> be secretive about or to boast off.
I can't help feeling that Roland was expressing himself ironically to
indicate self-deprecating modesty - I think that if you re-read his post
with that in mind you'll see his comments differently. Had this been a
binaries group, Roland could have used an ironic typeface to make this
clear.
--
PeterMcC
If you feel that any of the above is incorrect,
inappropriate or offensive in any way,
please ignore it and accept my apologies.
Sarcasm can be such a painful thing to get across with just plain text.
My points:
* createPopup isn't particularly nice route to take, due to compatability
reasons (and other things like you can only have one popup at a time) --
strictly speaking, "createPopup" and "standards compliant" in the same
sentece was a bit of a joke...
* There are thousands of people that have solved these problems, and
released them on open source if you just take the time to oogle that Google.
* Yes, we have solved the problem here, but as it's part of a product my
employer sells, I'd be out of a job if I did share the source code.
To save you half a second of effort, and assuming that you're using popups
for something along the lines of pseudo context menus:
http://www.google.co.uk/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=contex
t+menu+dhtml
David
(P.S. Please don't go there on the differences between browsers and
catering to the most widely used.)
Like Pop-up stopper from www.panicware.com ?
Anwho, we create the *same behaviour as createPopup*, but in a cross browser
manner to simulate context Menus (for the purpose of delivering an
application over the web without the need for ActiveX), so it's a part of
our emulation of a Win32 environment. We don't use createPopup itself,
though.
This allows our product to support NS/6+ and IE/5+ with a common codebase.
You probably don't want all the advertorial, but just imagine that we have a
full ad-hoc OLAP reporting tool that requires no software other than IE/5+
or NS/6+ installed on the client...
"David C Holley" <DavidC...@netscape.net> wrote...