creating a custom browser plugin image

Hilaire Fernandes hilaire at ofset.org
Sun Jul 15 12:13:31 UTC 2007


This is where I was stuck thanks.
I noted the font are a little tiny when switching to browser plugin 
image. Which option alter this?

Hilaire


Bert Freudenberg a écrit :
> Looks like the image tried to access 'http://test.st/'.
> 
> The most compatible solution is to add a BASE tag with the absolute URL 
> ending in a slash, which is concatenated with the SRC url (see 
> ProjectLauncher>>startUpAfterLogin and CodeLoader>>createRequestFor:in:).
> 
> You can try to add APISUPPORTED="TRUE" which will cause the image to try 
> fetching the (relative) SRC through the browser. That may or may not 
> work depending on which browser is used.
> 
> The problem is that a browser plugin cannot find out the base URL of the 
> page it is embedded in, so it cannot resolve relative URLs on its own. 
> The only way to fetch relative URLs is by going through the browser API. 
> Which was unreliable for years, hence at squeakland the APISUPPORTED tag 
> was generated on the server side by a script that used the Browser agent 
> string to determine if the API is supported or not.




More information about the Squeak-dev mailing list