When the custom formatter displays computed, it will display undefined, which is inconsistent with the actual situation.

[FreeLiC]

Vue version

3.5.13

Link to minimal reproduction

https://play.vuejs.org/#eNp9UE1Lw0AQ/SvLXtpCSJHgpbQFLRX0oKIeFySkk7h1v9idrYWS/+7shtQepLeZ997MvHknfudceYjAF3wZGi8dsgAY3VoYqZ31yE7MQ1swaSRuYkCrH6zXNSL4orHaRYQd61nrrWYTWjQRRpjGmoCsZis2SqbT2Wrd1irAbBRYBaWy3bTOyHI+nKfD1CBop2oE6pbzi4YXHAMNt7Ir98Easn0ShjHB0yGpwL84lLRc8AXLTOJqpezPU8bQRyhGvPmC5vsffB+OCRP81UMAfwDBzxzWvgMc6O37MxypPpPa7qIi9RXyDejxmDwOsvtodmT7QpfdPubwpek+wvaIYML4VDKalH3WC06Rb668/me3Kqs8J0xPKX4ewKedFGBV3pY3Fe9/AQ4urzs=

Steps to reproduce

1. open chrome devtools custom formatter;
2. view console;

What is expected?

Display the correct value

What is actually happening?

display undefined

System Info

No response

Any additional comments?

No response

[FreeLiC]

I think it should be modified like this, but I don't know if it is correct?

[yangxiuxiu1115]

I think it's as expected, there is a lazy feature in the computed attribute that calculates the value only when accessed, and this lazy calculation shouldn't be triggered in the custom formatter, so the displayed value is always undefined

playground

[Bayn-Web]

It's weird, because edge shows

[edison1105]

@Bayn-Web
You should first enable Custom formatters.

I agree with @yangxiuxiu1115, this is the expected behavior.