1741623 - React refs created by useRef() are not logged correctly before the DOM is loaded

Status: NEW

(DevTools :: Console, defect, P3)

Description

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

Attachment: feature.html

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

---

NOTE: This only happens on the first load of DevTools so reloading the page displays the values correctly.

Comment 1

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

Attachment: Firefox screenshot

Firefox seems unsure whether domRef.current is defined or not.

Comment 2

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

Attachment: Chrome screenshot

Chrome gets it right

Comment 3

[Julian Descottes [:jdescottes]]

Nicolas, can you find related bugs about expanding properties showing only current values.

Comment 4

[Nicolas Chevobbe [:nchevobbe]]

Looks like an issue between cache vs live messages

(In reply to Julian Descottes [:jdescottes] from comment #3)

Nicolas, can you find related bugs about expanding properties showing only current values.

It's Bug 1505304