Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #31789

Re: Why newly inserted area is not editable?

Show all headers | View raw

On Thursday, December 8, 2016 at 6:53:37 PM UTC-5, Thomas 'PointedEars' Lahn wrote:
> JJ wrote:
> 
> > previousSibling may not be an element node, depending on where you've
> > inserted the dynamically created TR element. You don't ignore that.
> 
> The “previousElementSibling” property introduced with DOM4 can provide an 
> easier workaround than an XPath expression (supported by an implementation 
> of DOM Level 2 XPath) or sibling node iteration.  Likewise, before one 
> writes an XPath expression, or attempts to iterate over child nodes, or 
> resorts to a library, one should check if the “firstElementChild”, 
> “lastElementChild”, or “children” properties are implemented that are 
> specified there.
> 
> <https://www.w3.org/TR/dom/#nondocumenttypechildnode>
> <https://www.w3.org/TR/dom/#parentnode>
> 

Thanks but problem resolved with making a specific ID content editable.

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Why newly inserted area is not editable? justaguy <lichunshen84@gmail.com> - 2016-12-08 13:39 -0800
  Re: Why newly inserted area is not editable? JJ <jj4public@vfemail.net> - 2016-12-09 06:25 +0700
    Re: Why newly inserted area is not editable? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-12-09 00:53 +0100
      Re: Why newly inserted area is not editable? justaguy <lichunshen84@gmail.com> - 2016-12-08 17:29 -0800
    Re: Why newly inserted area is not editable? justaguy <lichunshen84@gmail.com> - 2016-12-08 17:29 -0800

csiph-web