title: Why WAV format doesn't have same mimetype in different browsers?
body: <p>File input give different Mimetype for the same file in chrome or firefox. I have a wav file that I want to upload, chrome says it is <code>audio/wav</code> and firefox detect <code>audio/x-wav</code>.</p>
  
  <p>I know those two mimetype are very similar (<code>x-</code> stands for <a href="https://en.wikipedia.org/wiki/Media_type#Unregistered_x._tree" rel="noreferrer">non-standard</a>), but why are they handled differently in this case?</p>
  
  <p>Here is a fiddle to illustrate this: <a href="https://jsfiddle.net/r9ae0zfd/" rel="noreferrer">https://jsfiddle.net/r9ae0zfd/</a>. And here is the WAV file I used for this example: <a href="https://freesound.org/people/zagi2/sounds/391828/" rel="noreferrer">https://freesound.org/people/zagi2/sounds/391828/</a>.</p>
  
  <p>In the end the behavior that I would like is to take a <code>.wav</code> file from my computer (client) and send it by HTTP to my server as <code>audio/wav</code> regardless of the browser.</p>
  
  <p>There's a subsequent question to this: <em>how to harmonize this behavior?</em></p>