RE: [WSG] Comment mark
Hi Angus, The comment you use depends on the context. If you are in a PHP interpreted section, use /* ... */ (for a block comment), // or # (for commenting out the rest of a line). The syntax you are using works in (X)HTML and as John points out your syntax is incorrect. You also cannot have two dashes contained in the (X)HTML comment block. A correct example using both comment styles would be: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en"> My title Your IP is: Hope that helps, Kepler -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hayden's Harness Attachment Sent: Monday, December 10, 2007 12:41 AM To: WSG List Subject: [WSG] Comment mark I would like to appologize if I am off topic. I am not sure who to ask. I am using
Re: [WSG] Comment mark
Thanks, I didn't know that, I'm very knew to PHP :D Gonzalo González Mora On Dec 10, 2007 3:44 AM, Matthew Pennell <[EMAIL PROTECTED]> wrote: > On 12/10/07, krugonN <[EMAIL PROTECTED]> wrote: > > > > To comment a line in PHP code you should use // or you can comment a > > block using /* */ > > > > Or you can also use an octothorpe: # to comment out a single line in PHP. > > - Matthew > > *** > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > *** > *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Comment mark
On 12/10/07, krugonN <[EMAIL PROTECTED]> wrote: > > To comment a line in PHP code you should use // or you can comment a block > using /* */ > Or you can also use an octothorpe: # to comment out a single line in PHP. - Matthew *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Comment mark
It should be: (no 2nd !). On Mon, 10 Dec 2007 15:40:52 +1000, Hayden's Harness Attachment <[EMAIL PROTECTED]> wrote:
Re: [WSG] Comment mark
To comment a line in PHP code you should use // or you can comment a block using /* */ Gonzalo González Mora On Dec 10, 2007 2:40 AM, Hayden's Harness Attachment <[EMAIL PROTECTED]> wrote: > I would like to appologize if I am off topic. I am not sure who to ask. I > am using
[WSG] Comment mark
I would like to appologize if I am off topic. I am not sure who to ask. I am using
Re: [WSG] Browser test: Construct
On Dec 10, 2007, at 3:36 AM, Christian Montoya wrote:
To set FAYT to work automatically, add
user_pref("accessibility.typeaheadfind.autostart", true);
in your user.js
(or use about:config).
OK, I added "return false;" to the keybindings and successfully
repressed FAYT in FF on WinVista, but I don't know if that works in
all gecko browsers.
Gecko is Gecko :-)
I checked your page with Fx 2 and the nightly builds of both Camino
and Minefield: Fayt is not triggered.
Camino 1.5 appears not to 'get' it here, Fayt is triggered anyway.
I'll check if there is a known issue/limitation around that. But if I
were you, I wouldn't worry about it.
There are a few known bugs with keybindings in current nightlies on
Mac, but those should be fixed by the time Gecko 1.9 is released.
None affected your test page.
Philippe
---
Philippe Wittenbergh
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] Browser test: Construct
On Dec 9, 2007 3:21 AM, Philippe Wittenbergh <[EMAIL PROTECTED]> wrote:
>
> On Dec 9, 2007, at 4:37 PM, Christian Montoya wrote:
>
> > Is
> > there any way at all to prevent the FAYT behavior? If I apply "return
> > false," will that work?
>
> I don't know :-) Nobody ever managed to block FAYT, seen from here.
>
> To set FAYT to work automatically, add
> user_pref("accessibility.typeaheadfind.autostart", true);
> in your user.js
> (or use about:config).
OK, I added "return false;" to the keybindings and successfully
repressed FAYT in FF on WinVista, but I don't know if that works in
all gecko browsers.
--
--
Christian Montoya
christianmontoya.net
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] Browser test: Construct
On Dec 9, 2007, at 4:37 PM, Christian Montoya wrote:
Is
there any way at all to prevent the FAYT behavior? If I apply "return
false," will that work?
I don't know :-) Nobody ever managed to block FAYT, seen from here.
To set FAYT to work automatically, add
user_pref("accessibility.typeaheadfind.autostart", true);
in your user.js
(or use about:config).
Philippe
---
Philippe Wittenbergh
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
