| Summary: | Creating an element via DOM yields element with empty content | ||
|---|---|---|---|
| Product: | [WebTools] WTP Source Editing | Reporter: | Konstantin Komissarchik <konstantin> |
| Component: | wst.xml | Assignee: | wst.xml <wst.xml-inbox> |
| Status: | NEW --- | QA Contact: | Nick Sandonato <nsand.dev> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | nsand.dev |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 365774 | ||
|
Description
Konstantin Komissarchik
Hi Konstantin, This largely sounds like a style thing more than an actual problem, especially if the spec doesn't define a rule for this. If you had a patch to push us towards this, though, I'd be happy to take a look. Thanks. > This largely sounds like a style thing more than an actual problem Users do see it as a problem. It doesn't matter if its a style issue or not. Arguably Apache behavior is more reasonable as I can control what variant I get by either inserting a blank text node or not adding any children. > If you had a patch to push us towards this, though, I'd be happy to take a > look. I am afraid that I have no knowledge of SSE internals. The few times that I tried to dive in to debug things, I couldn't figure things out. There is an extra complication that I suspect the current behavior exists as a way to facilitate code completion, so if DOM behavior is changed to align with Apache, something would need to be done to get code completion working as originally intended. I think this issue requires attention of someone far more familiar with the code base than I am... |