Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #29015 > unrolled thread
| Started by | Martin Honnen <mahotrash@yahoo.de> |
|---|---|
| First post | 2015-12-14 18:03 +0100 |
| Last post | 2015-12-14 18:03 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.javascript
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Element output in JavaScript consoles Martin Honnen <mahotrash@yahoo.de> - 2015-12-14 18:03 +0100
| From | Martin Honnen <mahotrash@yahoo.de> |
|---|---|
| Date | 2015-12-14 18:03 +0100 |
| Subject | Re: Element output in JavaScript consoles |
| Message-ID | <n4mspc$sb5$1@news.albasani.net> |
Stefan Ram wrote: > I was looking for some DOM applications as examples for my > JavaScript course and came up with this use of the Firefox > console (input/output pairs): > > document.firstElementChild > <html> > I see that the Firefox console kinda »pretty prints« the > element. I.e., it does not just say > > [object] > > but > > <html> > > . I like this! But can I rely on it? > Do other browser consoles behave similar? Chrome outputs an expandable DOM tree representation of the element node, Edge does it similar to Chrome.
Back to top | Article view | comp.lang.javascript
csiph-web