*Anne van Kesteren*:
Instead of returning an uppercase six digit hex value I suggest
returning a lowercase value for compatibility with what UAs
(including IE) currently do
It may be the right decision on compatibility grounds, but other than
that lowercase hexadecimal digits (0-9, a-f)
*Anders Rundgren*:
But it is very hard to create certain types of applications without
having
modal dialogs.
That does not mean modal dialogs were a good idea, ever.
But it is very hard to create certain types of applications without
having modal dialogs.
That does not mean modal dialogs were a good idea, ever.
Christoph,
You are free to not use modal dialog in *your* applications.
You are also free to support end-users when windows magically
On 5 Sep 2006, at 12:54, Charles McCathieNevile wrote:
Instead of returning an uppercase six digit hex value I suggest
returning a lowercase value for compatibility with what UAs
(including IE) currently do
It may be the right decision on compatibility grounds, but other
than that
On Tue, 05 Sep 2006 19:07:35 +0200, Nicholas Shanks
[EMAIL PROTECTED] wrote:
On 5 Sep 2006, at 12:54, Charles McCathieNevile wrote:
Instead of returning an uppercase six digit hex value I suggest
returning a lowercase value for compatibility with what UAs
(including IE) currently do
It
On 9/5/06, Boris Zbarsky [EMAIL PROTECTED] wrote:
Shadow2531 wrote:
However, see http://shadow2531.com/opera/testcases/plugins/wmp/004.html
That works in Opera, but doesn't in Firefox. It seems that Firefox is
not using the codebase to resolve the data attribute before mapping it
to src.
Shadow2531 wrote:
If Firefox does use codebase to resolve data for WMP before mapping to
src
It does.
Right-clicking on the wmp window and choosing error details - more
information, will show C00D1197: Cannot play the file. That's
because WMP most likely only got
On Mon, 04 Sep 2006 19:37:30 +0200, Keryx webb [EMAIL PROTECTED] wrote:
To make the whole LI-element clickable I have to resort to CSS
( ul#nav li a { display: block } ) which does not work in all browsers
or JavaScript, which also is a hassle.
Yeah, li href=test/li does work in all browsers
Keryx webb wrote:
Will it break backwards compatibility? Yes, if todays browsers are
supposed to be able to render WHATWG-pages. But there are lots of other
things in WHATWG that they do not understand either. It's only the very
latest browsers that can handle canvas. No browser fully
Shadow2531 wrote:
The FF ( trunk or 1.5.0.6) codebase problem doesn't happen with Flash
as you can see from :
object type=application/x-shockwave-flash
codebase=http://www.adobe.com/;
data=shockwave/download/triggerpages_mmcom/flash.swf width=300
height=120/object
Hm OK. So there's probably
10 matches
Mail list logo
