I think you might get less push-back on whether a browser should aspire to being "innovative" if you draw finer distinctions about types of innovation.
There's a big difference between innovative idiomatic APIs, innovating the first support for new specs/standards, innovative performance improvements, innovative UI/X, innovative plugin/extension engines, and (unfortunately) innovative interpretations of specs/standards.
There's a big difference between innovative idiomatic APIs, innovating the first support for new specs/standards, innovative performance improvements, innovative UI/X, innovative plugin/extension engines, and (unfortunately) innovative interpretations of specs/standards.