This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6821 - moki: generalize the objectInfo element
Summary: moki: generalize the objectInfo element
Status: NEW
Alias: None
Product: mobileOK Basic checker
Classification: Unclassified
Component: Java Library (show other bugs)
Version: unspecified
Hardware: Other Windows 3.1
: P2 enhancement
Target Milestone: ---
Assignee: Dominique Hazael-Massieux
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 6820
Blocks:
  Show dependency tree / graph
 
Reported: 2009-04-16 12:40 UTC by fd
Modified: 2012-12-04 00:52 UTC (History)
0 users

See Also:

Attachments

Description fd 2009-04-16 12:40:09 UTC 
Description
-----
The Object Element Processing Rule required us to introduce the loadType attribute on the objectInfo element.

This works fine but requires the Resource class to process objects with a special rule, and I'm trying to generalize stuff when they can be.

The loadType attribute can take 3 values: SKIPPED, TASTED and RENDERED (default value). This could apply to other resources as well, e.g. TASTED could be used for images if their content-type is not supported by a browser.


Solution
-----
We could promote the loadType attribute of the objectInfo element to either a generic loadType element or to a loadType attribute on, say, the URI element. I'm more inclined to have a separate loadType element.

Since the type attribute of the objectInfo carries the exact same information as the imageInfo type attribute, then provided bug 6820 is fixed, the objectInfo element would then not be needed at all.