[Bug 5846] Accessing Object Parameters from an Embedded SVG

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5846





--- Comment #8 from Jeff Schiller <codedread@gmail.com>  2008-07-16 22:48:48 ---
"That's not a use case, it's an example of how it could be used. What I mean by
use case is an actual example of an actual site that is currently working
around the lack of this feature, or that would be able to do something
dramatically better if this feature was available."

Use Cases should not be limited to only 'actual examples', especially since
that limits your use cases to things that are only currently achievable.  But
in the interest of continuing the discussion...

I've already mentioned that my own site wants to use this and I've worked
around this missing feature.  See the menu.svg object at codedread.com.  The
way I worked around it was by making a soft-link on my webserver so that the
pages appear to be on the same domain.  Since I don't have SSH access to my
webserver, the way I had to make this soft link was to create a special PHP
file which would do the soft-link for me (one time).  What a pain.  What a
virtual non-starter for non-technical users to do such things.  What a literal
non-starter for files on truly different domains/web servers.

Google AdSense is another example.  Instead of including a single HTML file
from Google's servers and then sending it parameters, I have to monkey around
with script elements, whose JS variables pollute my scripting space.  Then I
have to include a 21kb script in my page for every ad
(http://pagead2.googlesyndication.com/pagead/show_ads.js).

"it is far too early to worry about that kind of optimisation for a technology
as young as SVG-in-HTML"

We shouldn't call this "SVG-in-HTML", since that term is typically used to
refer to inline SVG within text/html.  This problem exists with referenced
SVG/HTML content in HTML or XHTML.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 16 July 2008 22:49:30 UTC