thx for feedback, you are completely right ( Accessibility is really big :-)) but I think I didn´t explain myself very good.
I am not talking about executing primary button when it is focused.
The question is about still having a form field focused where you need to enter information. Is it ok to block executing primary button (which is standard browser behaviour) by clicking enter there in the form field?
The action of executing the primary button could be still done blocking this functionality by jumping with tabulator to the primary button and then clicking enter
This is how it behaves normally:
Imagine you fill in data in a register form where you enter your email adress. When you click enter primary button is automatically executed (e.g. firefox on ebay or amazon)
Here one reason why I learned not to manipulate browser behaviour:
You have to handle it in different browsers and you can´t assure that solution works in future versions/updates of the browser