dear all
even is if / is repeated more than once in any URL, it is interpreted by
most browsers as just one /
You can try this on any site you visit which has subfolders.but if the
website is using a external CSS and images in another subfolder it won't
show.
for e.g. the pages is domain.com/page
Hi
That's a common enough response when dealing with standards based
implementations from companies that either:
* do know and don't care
* don't know and are scared/worried
* do know, do care but don't have the resources
* do know but implementation would have internal political implications
(I'v
On Fri, 1 Feb 2008 11:10:04 +1000, Taco Fleur wrote:
> On a different note:
> Just been speaking with ScanAlert, I tried to get them to understand that
> their code
> does not validate since they used oncontextmenu, and border="0" - I got a
> response
> saying that W3C standards is not widely acc
CTED] [mailto:[EMAIL PROTECTED] On
Behalf Of James Ellis
Sent: Friday, 1 February 2008 8:45 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] linking to images with //
Hi
It's a bit difficult to work out what is going one given the image itself
seems to be a 1x1 transparent gif. You may
ooh sorry, I thought it had to do with standards...
My apologies. Thread closed.
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Adam Martin
Sent: Friday, 1 February 2008 11:17 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] linking to images with //
Can we please
they presented it, I got some
> 404
> errors from browsers looking for the image on our domain.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Brian Cummiskey
> Sent: Friday, 1 February 2008 9:46 AM
> To: wsg@webstandardsgr
On a different note:
Just been speaking with ScanAlert, I tried to get them to understand that
their code does not validate since they used oncontextmenu, and border="0" -
I got a response saying that W3C standards is not widely accepted!
Microsoft is not using it, Google is not using it and all
February 2008 9:46 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] linking to images with //
Anders Nawroth wrote:
>
> "//" in the beginning of the URI says this is a network path.
> I have no idea of how the browser support for this is, or how they
> choose to int
I placed the code on the pages without really paying attention to it, after
> a while I discovered the image was linked as
> src="//images.scanalert.com/meter/www.clickfind.com.au/12gif"
> I never seen this before, but it worked! I changed it to src="
> http://images.scanalert.com/meter/www.clickfi
>In the other discussion it was more around how to deal with http and https
CSS images references when the image was remote. The accepted solution goven
by all was to use two different CSS files. My friend Ryan Joy noted
(http://www.atxryan.com/2008/01/22/breaking-with-protocol/
) that using this '
Well, thats the question here.
It seems to work without in some browsers (if I'm not mistaken).
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of kate
Sent: Friday, 1 February 2008 8:31 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] linking to images
On Jan 31, 2008, at 5:17 PM, Anders Nawroth wrote:
"//" in the beginning of the URI says this is a network path.
I have no idea of how the browser support for this is, or how they
choose to interpret it.
A single "/" in the beginning says this URI is relative to the
domain of the document
Anders Nawroth wrote:
"//" in the beginning of the URI says this is a network path.
I have no idea of how the browser support for this is, or how they
choose to interpret it.
scanalert/hackersafe publishes their badges with the src="//path/image.gif" /> method.
I've yet to see a problem w
Hi,
Should'nt that be
James Ellis skrev:
"Relative URI references are distinguished from absolute URI in that
they do not begin with a scheme name. Instead, the scheme is
inherited from the base URI, as described in Section 5.2."
"//" in the beginning of the URI says this is a network path.
I have no idea of
Hi
It's a bit difficult to work out what is going one given the image itself
seems to be a 1x1 transparent gif. You may find that your browser is blocking
these as they most likely represent "web bugs", causing the issue you see.
the HTML spec redirects URI info to RFC2396. In section "3. URI Sy
16 matches
Mail list logo
