9930 - Need to separate the DOM from RDF

Status: VERIFIED FIXED

(Core Graveyard :: RDF, defect, P3)

Description

[Chris Waterson]

This has to do with the recent in-line editing changes. RJC, I'm assigning this
to you, although I think you and I will need to work together to figure out how
exactly we want to do this. Just creating this bug as a placeholder to track.

Comment 1

[Robert John Churchill]

For the short term, how about if we start with taking out the "annoyance
assert"?

Comment 2

[Chris Waterson]

Or what if we made it trigger off of the right mouse click? I'm really nervous
about removing the assert, because we basically know that this code is cheating
as it is right now...

Comment 3

[Robert John Churchill]

Right mouse button?  What's that?  <grin>

Right mouse clicks currently bring up a context menu... I don't want that to go
away.

I think we can use this open bug to track the problem instead of an assert that
throws everyone into the debugger. We can add the assert back into the code
path once we have updated the code to do whatever we decide is appropriate.

Just my opinion though.

Comment 4

[Robert John Churchill]

One too many breaks into the debugger have forced me to comment out this
assertion for the short term until the code is rewritten.  :^)  I'm leaving this
bug open as an indicator that changes to the content model shouldn't update RDF's
graph (unless its a persistant attribute change).

Comment 5

[Robert John Churchill]

I'm changing this bug's summary to be "Need to separate the DOM from RDF" for
that's the real task at hand.

Comment 6

[Robert John Churchill]

Chris has landed the changes to separate the DOM from RDF.

Comment 7

[phillip]

code level fix, marking verified.