It might not be a bug in the sense that it's a spec violation, but it's behavior that every other browser I've used for 15 years has. If this were a commercial

It might not be a bug in the sense that it's a spec violation, but it's behavior that every other browser I've used for 15 years has. If this were a commercial product (my wiki), there would be a bug in the tracker for it :) In the link people have given JS workarounds.