[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Question: object onload param
Hi, The current WebCGM 2.0 specification says the following about the 'onload' param (of the Object tag): - [...] allows script writers to manipulate the WebCGM DOM at the point at which the user agent has fully parsed the object tag and its descendants and is ready to render the object to the screen. Ralf and I interpreted this differently. One of us thought it meant that the onload would be dispatch when the ActiveX is loaded, and the other thought that it meant the onload is dispatched when the Metafile is loaded? There is a difference. From a technical perspective the ActiveX can be loaded without a CGM file (as long as the MIME type is specified on the 'object' tag, the ActiveX will be created). We noticed the problem when trying the WebCGMEvent test. The 'src' attribute is actually set in the script that is called via the onload param. So when should we dispatch the onload event? We see advantages to both interpretations: i) When the ActiveX is loaded... allows to set the 'src' parameter in the onload event handler or alternatively, possibly modify via the DOM the CGM before the first display. ii) When the Metafile is loaded... is like a DOM Mutation event where you get notified that the document has change. In this case you would get the onload every time the 'src' attribute is set or for each internal link to a new WebCGM file. The use case here is to extract metadata information to be interpreted by the host application following each load. What was the intent? Which is needed? Regards, -- Benoit mailto:benoit@itedo.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]