Seems like it would be easy enough to parse that out yourself.
I don't know why MSHTML would want to have the dom link to the raw text. Seems rather heavy.
Dave: I'm not sure what you mean by "Parse it out". It would sound reasonalbe if I could at least get the index in teh HTML where the selection was starting from, but that's not possible. Even if it was, it'd be hard to figure out what length of a string to "parse out" of the original HTML I would need, as the range selection string differs greatly in content and length..
Filip: I'm not sure that would solve my problem because:
1) Some of the attributes may be in a different order than the original HTML - can tidy organize attributes by name?
2) even if I did - I want to be able to find the exact piece of *original* HTML text that was selected in the broweser control. I can't give back a Tidy'ed HTML as a result as it will not match the original HTML.
Thanks for trying.
Roy.
i faced the same problem, and the problem was when u view the source of the webBrowser u get what is like class="xxx" but if u selected it and retreive it in the above method it return class=xxx, i had a solution but i dont know yet how to do it is if i can programiticly select all the text in the webbrowser and then get them in a string... this is the only way to get them match
Do we know what the differences in the HTML are exactly? As far as I can see, the only differences are uppercase tag names and missing quotes for the class attribute. Surely these are trivial to correct?