Internet Explorer 7

From SynchroEdit

(Difference between revisions)
Jump to: navigation, search
Revision as of 15:52, 11 April 2006 (edit)
Kalle Alm (Talk | contribs)

← Previous diff
Revision as of 20:46, 29 September 2006 (edit)
Kalle Alm (Talk | contribs)
(Removed invalid reference to XUL (dear god, that's old).)
Next diff →
Line 8: Line 8:
Failing that, it may be necessary to write an ActiveX component or similar using the .NET framework as an Explorer-only solution, though it would naturally be more efficient to make use of the already-existing solution. For further information on this alternative solution, see [[Internet Explorer 6]]. Failing that, it may be necessary to write an ActiveX component or similar using the .NET framework as an Explorer-only solution, though it would naturally be more efficient to make use of the already-existing solution. For further information on this alternative solution, see [[Internet Explorer 6]].
- 
-Additionally, the current implementation is using XUL, a Mozilla-only technology, which will have to be rewritten. The usage of XUL at the core is very limited, and this should not be a major obstacle. 
Also see: [[Internet Explorer 6]]. Also see: [[Internet Explorer 6]].

Revision as of 20:46, 29 September 2006

Internet Explorer 7 implementation strategy

This document describes the strategy for implementing SynchroEdit in the upcoming release of Internet Explorer (version 7).

The current implementation of SynchroEdit is based on the W3C mutation-events standard found here.

Mutation-events enable the developer of a script the ability to track changes to the DOM tree by way of event-handlers. As no currently released versions of Internet Explorer support mutation-events, this is definitely an issue. However, mutation-events have only recently been implemented into the alternative browsers (such as Firefox), and with the upcoming release of Internet Explorer 7.0 (see this page), we can only presume that the DOM mutation events, with the amount of publicity that they have received recently, have been a prioritized implementation.

Failing that, it may be necessary to write an ActiveX component or similar using the .NET framework as an Explorer-only solution, though it would naturally be more efficient to make use of the already-existing solution. For further information on this alternative solution, see Internet Explorer 6.

Also see: Internet Explorer 6.

Personal tools