We are planning on implementing the omnibox API so that it can alter the awesome bar. After that we could probably do with a little more detail on this bug to figure out what it is people want to do with the awesome bar (assuming that's what is meant by location bar). Not sure what to do with this bug to be honest.

Can you provide any link to the arguments that factored on the decision to deny it?

From what I remember: The bug has no description so currently is too vague to be helpful. The omnibox API has provided some API to do some things. As for what else could be done here... we'd need some help specifying that and building out an API. Further, the location bar is XUL and so something we have a lot of concerns about getting into. Since this bug this email came out https://mail.mozilla.org/pipermail/firefox-dev/2016-December/004894.html and it was mentioned in there that might include some WebExtensions API support. If it did, perhaps from that some new bugs will get filed that are more actionable.

thank you!

Such silent wontfixing is really misleading, so it probably makes sense to post a clarification comment in such cases by default, without the need for people to be unreasonably disappointed and to ask questions. And actually, if a bug is going to be closed not because there are no plans to fix it, but because its description is just incomplete or not clear enough, then the bug should probably not be closed until a new replacement bug is filed so that people would not be confused. BTW, IIRC, there is the “INCOMPLETE” keyword in Bugzilla, and this keyword is probably much more suitable and informative than “WONTFIX” in such cases.