Andreas Hochsteger schrieb:
Hello,
Using plain IE (6.0.2900.2180.xpsp_sp2_gdr.05031-1519) I got a security
warning, that active contents have been deactivated.
Same thing here with IE 6.0.2900.2180.xpsp_sp2_gdr.050301-1519, displays
just fine.
The security warning comes from the onload=...
hepabolu wrote:
Sylvain Wallez wrote:
Can you build a standalone xhtml file that reproduces the problem?
Here it is. It works fine in firefox (both windows and mac) and safari,
but it produces the error I mentioned before in IE6.
Are you by chance serving it up with an XML mime-type?
Jason Johnston wrote:
hepabolu wrote:
Sylvain Wallez wrote:
Can you build a standalone xhtml file that reproduces the problem?
Here it is. It works fine in firefox (both windows and mac) and
safari, but it produces the error I mentioned before in IE6.
Are you by chance serving it up
hepabolu wrote:
On Sun, 6 Nov 2005, Sylvain Wallez wrote:
[X] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it as the
beginning of widget names)
Guys,
I
Sylvain Wallez wrote:
Entity names, PI targets, notation names and attribute values declared
to be of types ID, IDREF(S), ENTITY(IES) or NOTATION cannot contain
any colons. Error processing resource 'http://localhost:/myform.form'
What is displaying this message? Is it Cocoon, a parser,
Sylvain Wallez wrote:
Can you build a standalone xhtml file that reproduces the problem?
Here it is. It works fine in firefox (both windows and mac) and safari,
but it produces the error I mentioned before in IE6.
Bye, Helma
Title: OSN - Zoek modellen
Veel succes!
On 28.11.2005 23:50, hepabolu wrote:
Can you build a standalone xhtml file that reproduces the problem?
Here it is. It works fine in firefox (both windows and mac) and safari,
but it produces the error I mentioned before in IE6.
Works for me: IE 6, Win 2k.
Jörg
Joerg Heinicke wrote:
On 28.11.2005 23:50, hepabolu wrote:
Can you build a standalone xhtml file that reproduces the problem?
Here it is. It works fine in firefox (both windows and mac) and
safari, but it produces the error I mentioned before in IE6.
Works for me: IE 6, Win 2k.
Jörg
On 11/28/05, hepabolu [EMAIL PROTECTED] wrote:
Joerg Heinicke wrote:
On 28.11.2005 23:50, hepabolu wrote:
Can you build a standalone xhtml file that reproduces the problem?
Here it is. It works fine in firefox (both windows and mac) and
safari, but it produces the error I mentioned
I got an error using WinXPPro with Firefox 1.5 (2005-11-07) in an IE-Tab
(1.0.6.3) (https://addons.mozilla.org/extensions/moreinfo.php?id=1419).
Using plain IE (6.0.2900.2180.xpsp_sp2_gdr.05031-1519) I got a security
warning, that active contents have been deactivated.
Plain Firefox is ok.
On Sun, 6 Nov 2005, Sylvain Wallez wrote:
[X] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it as the
beginning of widget names)
Guys,
I suppose this was the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 6 Nov 2005, Sylvain Wallez wrote:
[X] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it as the beginning of
Sylvain Wallez wrote:
So please choose one proposal below:
[+1] foo.bar:input (colon, not CSS-friendly because of IE)
[-1] foo.bar..input (double period)
[-1] foo.bar.input. (trailing period)
[-0] foo.bar._input (underscore, requires to forbid it as the
beginning of widget names)
Vadim
Le 7 nov. 05, à 08:36, Sylvain Wallez a écrit :
...So I kindly ask people to carefully read and understand the
rationale and motivation behind ':'.
Ok, thanks for your (repeated I think ;-) explanation, then:
[+1 ] foo.bar:input (colon, not CSS-friendly because of IE)
-Bertrand
Il giorno 07/nov/05, alle ore 08:36, Sylvain Wallez ha scritto:
So I kindly ask people to carefully read and understand the
rationale and motivation behind ':'.
Alright, you convinced me. I hereby revert my previous vote and vote
+1 on using the colon.
Ugo
--
Ugo Cei
Tech Blog:
Sylvain Wallez wrote:
The initial foo.bar:input proposal *structucally* prevents name
all crispy clear now.
I revert my previous +1 and +1 this proposal instead.
Jorg
Sylvain Wallez wrote:
[X] foo.bar._input (underscore, requires to forbid it as the beginning
of widget names)
Jeroen
On Sun, 2005-11-06 at 11:51 +0100, Sylvain Wallez wrote:
So please choose one proposal below:
[ ] foo.bar:input (colon, not CSS-friendly because of IE)
+1
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java XML Competence Support Center
Jorg Heymans wrote:
Sylvain Wallez wrote:
The initial foo.bar:input proposal *structurally* prevents name
all crispy clear now.
Phew! Sometimes, when there's a lot of background, producing a clear
explanation is not an easy task ;-)
Now I'm glad I finally was able to do it,
Hi all,
[X] foo.bar:input (colon, not CSS-friendly because of IE)
+1 from me as well. It's the least evil one, it does interfere with the
libraries meaning of :, however, since it is in effect hidden from the user,
it's okay.
Best regards,
Max Pfingsthorn
Hippo
Oosteinde 11
1017WT
Hi,
[+1] foo.bar:input (colon, not CSS-friendly because of IE)
(do people still use IE? ;-)
Andrew.
--
Andrew Savory, Managing Director, Luminas Limited
Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135
Web: http://www.luminas.co.uk/
Orixo alliance: http://www.orixo.com/
On Nov 7, 2005, at 3:26 AM, Sylvain Wallez wrote:
Jorg Heymans wrote:
Sylvain Wallez wrote:
The initial foo.bar:input proposal *structurally* prevents name
all crispy clear now.
It was clear then. As always there are trade offs. In this case Its
between possible naming conflicts and
Sylvain Wallez wrote:
So please choose one proposal below:
[X] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it as the beginning
of widget names)
--
Leszek
Andrew Savory wrote:
Hi,
[+1] foo.bar:input (colon, not CSS-friendly because of IE)
(do people still use IE? ;-)
only a 90% minority does :)
--
Leszek Gawron [EMAIL PROTECTED]
IT Manager MobileBox sp. z o.o.
+48
Ezkovich Glen wrote:
snip/
Phew! Sometimes, when there's a lot of background, producing a clear
explanation is not an easy task ;-)
Now I'm glad I finally was able to do it, and will make sure this is
written in the docs, to avoid the same effort later in the future :-)
as opposed to sooner
Hi all,
In order to finally get 2.1.8 out, we have to define once the naming
rule for HTML IDs generated by the CForms stylesheets.
Let's give some background for those who haven't followed the discussion.
CForms stylesheets produce container elements for fields, that include
the input
Sylvain Wallez wrote:
So please choose one proposal below:
[ ] foo.bar:input (colon, not CSS-friendly because of IE)
[X] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it as the
beginning of widget names)
My preference
Sylvain Wallez wrote:
So please choose one proposal below:
[ ] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it as the beginning
of widget names)
Sorry for
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
So please choose one proposal below:
[ ] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it as the beginning
of
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
So please choose one proposal below:
[ ] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it
Sylvain Wallez wrote:
[X] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it as the beginning
of widget names)
Cast your votes!
As I would never use CSS rules
On Nov 6, 2005, at 2:51 AM, Sylvain Wallez wrote:
[ ] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[X] foo.bar._input (underscore, requires to forbid it as the
beginning of widget names)
* Sylvain Wallez:
The main point being that this rule *must* ensure that
generated IDs can never conflict with widget full names (e.g.
foo.bar-input would potentially conflict with a bar-input
widget sibling of bar).
Then why don't you use a « reserved » keyword inbetween,
Sylvain Wallez wrote:
[x] foo.bar._input (underscore, requires to forbid it as the beginning
of widget names)
Jorg
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
So please choose one proposal below:
[ ] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
So please choose one proposal below:
[ ] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ]
Il giorno 06/nov/05, alle ore 11:51, Sylvain Wallez ha scritto:
[ ] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ X] foo.bar._input (underscore, requires to forbid it as the
beginning of widget names)
Reinhard Poetz wrote:
Sylvain Wallez wrote:
[X] foo.bar:input (colon, not CSS-friendly because of IE)
[ ] foo.bar..input (double period)
[ ] foo.bar.input. (trailing period)
[ ] foo.bar._input (underscore, requires to forbid it as the
beginning of widget names)
Cast your votes!
As I
Jean-Baptiste Quenot wrote:
* Sylvain Wallez:
The main point being that this rule *must* ensure that
generated IDs can never conflict with widget full names (e.g.
foo.bar-input would potentially conflict with a bar-input
widget sibling of bar).
Then why don't you use
On 06.11.2005 23:11, Sylvain Wallez wrote:
As I would never use CSS rules based on IDs as they are a moving
target IMHO I don't have a problem with it. And if I really had to,
there is at least some workaround IIUC. The other options are really
ugly. So +1 for the first.
I change my vote:
On Nov 6, 2005, at 4:13 PM, Sylvain Wallez wrote:
Jean-Baptiste Quenot wrote:
* Sylvain Wallez:
The main point being that this rule *must* ensure that
generated IDs can never conflict with widget full names (e.g.
foo.bar-input would potentially conflict with a bar-input
Le 7 nov. 05, à 02:05, Ezkovich Glen a écrit :
...An alternative naming would be along the lines of foo.bar.cf_input.
While not following the more general convention it comes close. (I'm
sure someone will confuse it for a column name ;-).)
While there remains clutter it is significantly
Bertrand Delacretaz wrote:
Le 7 nov. 05, à 02:05, Ezkovich Glen a écrit :
...An alternative naming would be along the lines of
foo.bar.cf_input. While not following the more general convention it
comes close. (I'm sure someone will confuse it for a column name ;-).)
While there remains
43 matches
Mail list logo
