# STR
1. Load the attached document (`feature.html`) with the DevTools closed.
2. Press `[option]` + `[command]` + `[k]` to open the Web Console.
You will see that the Web Console correctly reports `domRef.current = undefined` but the `domRef` object is then logged showing that `domRef.current` is defined.
Confusingly, logging `domRef.current` again shows that the object is, in fact, still `undefined`:
---
`domRef.current` = `undefined`
`domRef` = `> Object {.current: p + }`
`domRef.current` = `undefined`
---
Bug 1741623 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
# STR 1. Load the attached document [feature.html](https://bugzilla.mozilla.org/attachment.cgi?id=9251152) with the DevTools closed. 2. Press `[option]` + `[command]` + `[k]` to open the Web Console. You will see that the Web Console correctly reports `domRef.current = undefined` but the `domRef` object is then logged showing that `domRef.current` is defined. Confusingly, logging `domRef.current` again shows that the object is, in fact, still `undefined`: --- `domRef.current` = `undefined` `domRef` = `> Object {.current: p + }` `domRef.current` = `undefined` ---
# STR 1. Load the attached document [feature.html](https://bugzilla.mozilla.org/attachment.cgi?id=9251152) with the DevTools closed. 2. Press `[option]` + `[command]` + `[k]` to open the Web Console. You will see that the Web Console correctly reports `domRef.current = undefined` but the `domRef` object is then logged showing that `domRef.current` is defined. Confusingly, logging `domRef.current` again shows that the object is, in fact, still `undefined`: --- `domRef.current` = `undefined` `domRef` = `> Object {.current: p + }` `domRef.current` = `undefined` --- NOTE: This only happens on the first load of DevTools so reloading the page displays the values correctly.