You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SPECIFICATION BUGS ONLY - Description =====================================
Right now, the spec says that all relative URI's in a gadget spec are relative to the gadget specs URL... the challenge is, this URL can vary depending on how it is registered and stored. For consistency, we should allow a gadget developer to specify the Base URL for all relative URI's in the gadget specification by using an xml:base attribute on the Module. e.g.
This allows a module to be completely portable with regards to relative URI resolution.
Document affected: ================== 1.) Please attach a patch for the document if appropriate. 2.) Post a thread at http://groups.google.com/group/opensocial-and-gadgets-spec/topics linking to this issue report. 3.) Post a comment on this issue, linking back to the thread.
Original author: [email protected] (April 06, 2012 21:05:44)
SPECIFICATION BUGS ONLY - Description
=====================================
Right now, the spec says that all relative URI's in a gadget spec are relative to the gadget specs URL... the challenge is, this URL can vary depending on how it is registered and stored. For consistency, we should allow a gadget developer to specify the Base URL for all relative URI's in the gadget specification by using an xml:base attribute on the Module. e.g.
<Module xml:base="http://example.org/">
...
</Module>
This allows a module to be completely portable with regards to relative URI resolution.
Document affected:
==================
1.) Please attach a patch for the document if appropriate.
2.) Post a thread at
http://groups.google.com/group/opensocial-and-gadgets-spec/topics
linking to this issue report.
3.) Post a comment on this issue, linking back to the thread.
Original issue: http://code.google.com/p/opensocial-resources/issues/detail?id=1294
The text was updated successfully, but these errors were encountered: