[Bug Report][3.1.2] v-text-field details slot - not replacing default content

[marcpaskell]

Environment

Vuetify Version: 3.1.2
Vue Version: 3.2.45
Browsers: Chrome 109.0.0.0
OS: Mac OS 10.15.7

Steps to reproduce

Add a #details slot to a v-text-field

Expected Behavior

Content of slot replaces everything in that area

Actual Behavior

Content of slot is placed in between errors and counter...

Reproduction Link

https://codepen.io/pasco82/pen/YzjLMvV?editors=1011

[hostafrica]

Can confirm that it's still an issue on vuetify version: 3.1.7

[lioneaglesolutions]

Not 100% sure if the slot is designed to take over the whole messages section - I would assume it does. Is it as simple as checking if the slot is present before rendering VMessages @johnleider ?

vuetify/packages/vuetify/src/components/VInput/VInput.tsx

Lines 176 to 187 in 9536451

	{ hasDetails && (
	<div class="v-input__details">
	<VMessages
	id={ messagesId.value }
	active={ hasMessages }
	messages={ messages.value }
	v-slots={{ message: slots.message }}
	/>
	{ slots.details?.(slotProps.value) }
	</div>
	)}

[kappaflow]

Can confirm the issue with v.3.2.4. I can't properly use v-slot for hint because of an empty block that takes space.
Have to use:

<template v-slot:details>
  <div class="!absolute v-messages">
    Some text with a <a href='#'>link</a>
  </div>
</template>

[johnleider]

Vuetify Play reproduction: https://play.vuetifyjs.com/#eNrFVc1u00AQfpXpghSbxHabIiRCWqUHDhyQEEIc8LqSa0+apfba7G7SltTvznhtV46TVkUcyMnz983MNzObcMsuytLfrJHN2NxgXmaxwXMuAeYbLy5L+2mFZaHyVrJyUkgTC4nqUWnVqrjtKVrPrK8BIIU+4+xkytmuQeekfrer3UGzeAbvjLcUmKW7JoCNlxcpZgRihMlwCA8wU+sM69yh/fAV/loLhekEGjkp1tKgivYjs/jKAn87DNwG7uVDpQrl5ah1fN0kHl2p4gbl6ECOPL7LUF6bFflNj4f2ARFERTcveJUizcKSugWhv8eZSKHibC8EYNtzqMADvSrWWQpmJTQUGypXpEgSAkpDzECDDBoTIwq5V0LQ25ln6mvpOVCPQW2EvH4WeNfQX4DdVSMTrdagkv+0gJgTbX+/gDbsmfX76B3CDZ7goa/pH2bjsXu/te7xxmuhuf7BhOc6UaI0tA9m3TwOIi8LZWALCpdQwVIVOYzoQRk1Y6A02oA9RziD0ReFmciFjNU9BdSR5Nd52eZrr57O0kK6bVNlx9cMNnG2JshzODpqPh8eYPS1NfujSePfLl7P3X74zZ3B/Aymxzbyc3xXfyarWMUJRegOwRbVi28L6eorY0PekioMLh0nvJyfO27IecTp508+zDjXC86isUPi01b3jfvgcOaPOXPdhUPOYXjsvY+2J5PTqo58gRARhBPG3u8L7wfnXq0fk4M7bnXRdjqpXPd10DWgaIZUeduBX1+iY9t0LSOfJAn0TKBdOd/OBKCytFT1YjSrQEvAJqzZAvIs/Z+6kPRvYnnirUFzNuuY44y2o5Y5WxlT6lkQJKmkMDocsVG+RBPIMg8W5BYoGp/I0UuLfHHqn/rTIBXa9NU+6tyjN/VWoyIQztq52TRGLO9fkKr1pAxT/22ToVV5dHh0lTrfgw4oH72XnkKZoqKn/4UdDcL6XQ1Me521zFfEdybkjR5QnWhLc9gV+U8tW7AaKaoTVhNm66TMNoBFfwCcbm3M

[KaelWD]

I think the reason for this is VTextField always passes a details slot for the counter, if the details slot replaced messages then VTextField would have to reimplement messages too.