On Oct 23, 2009, at 11:38 AM, Marcelo wrote:

>
> On Oct 23, 6:26 pm, Gregory Short <[email protected]> wrote:
>>
>> Except web browser != html viewer...
>
> Quite right, but 'HTML viewer' == 'Browser Control', which is commonly
> used in desktop applications written in VB, Delphi, C++, etc., and
> that is allowed.
> What you may not do is to embed the image with a resource ID, because
> that means that you're displaying an attachment inline rather than
> fetching the image by HTTP.

True enough...I suppose it's just a matter of *who* is telling the  
email client the url to fetch. The end-user can't do it, but the  
person crafting the email can, and by those means it *can* be directed  
to an arbitrary url. Although I'm not entirely convinced that your  
equality is entirely true, on account of the question of what happens  
when you click a link. In a "regular" browser control, if you click a  
link, it's followed in that control (in general). On the other hand,  
email clients generally strictly render the html, but provide no  
support for interacting with it beyond opening a clicked link in an  
actual web browser. The only thing preventing a user from visiting,  
for example, google.com in Random Desktop App A is that there is no  
way to type in a url, and there are no links to let the user escape  
the network of documents prescribed by the developer. Whereas with a  
mail client, even if there is a link to google.com, clicking it will  
*not* open it in the email client. I'm sure there's a counter-example  
out there, of course, but showing that an email client *can* act as a  
web browser does not mean that all email clients *do* act as web  
browsers.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-maps-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to