This can also be seen in a more simple way.
When creating a world, enabling 'Always Day' disabled 'Do Daylight Cycle' (which it should), but then disabling 'Always Day' after doing that also enables 'Do Daylight Cycle' (which it shouldn't).
Also affects 1.12.0.
I believe the difference between Bedrock and Java sensitivity is because Java uses raw mouse input, while Bedrock uses Windows Pointer Speed. For example, Bedrock sensitivity has mouse acceleration when the "enhance pointer speed" setting is enabled, but Java sensitivity does not (except in 1.14.3, which was a bug and was fixed).
For me, the mouse acceleration seems to be a result of the "Enhance Pointer Precision" Windows system setting. If you turn it off, the mouse acceleration turns off. This (making Minecraft affected by system mouse acceleration) might actually be a cool feature, but there should be a setting to disable it without disabling it for your entire computer.
The 'Affects Version' tag is outdated, but I can confirm that this still happens in 1.9.0.
Should this be marked as 'Fixed' and 'Resolved'?
I'm experiencing it in 18w47a.
I gave it like about 20 fish originally. I tried it just now again and it ate an entire stack of raw fish and it still didn't tame.
oh... ok. Thanks for telling me; I feel stupid now. Thanks for letting me know.
Interestingly enough, if you go into a river (or other water) on Java Edition 1.15.2, the current music stops, but underwater music generally does not start for several minutes. To my knowledge, both Java and Bedrock have timed (not continuous music), but I also tested on Bedrock 1.16.0, and the underwater music starts immediately after going underwater. So while the issue is present on both editions, it is much more tolerable on Java Edition since the underwater music won't actually start unless you're underwater for a long period of time, whereas on Bedrock, just going underwater for a second starts the music.