On a sudden realization, I found that we are including something into another <custom.View> and creating a new file for this included content inside a <merge>. Instead, we can have the <custom.View> as the parent element. I'm not sure if this can provide a performance win, but the code looks more elegant.
Created attachment 583421 [details] [diff] [review] Patch This patch remove 2 files in layout-v11/. One of the files have been renamed for better naming convention. A new file is added to separate the "awesomebar_search" related UI. As expected, the code looks better and clearer (than having an "action_bar") file separately. I haven't checked it against any performance win -- but we should have some for sure. :)
Comment on attachment 583421 [details] [diff] [review] Patch Looks good to me. Getting Brad for a second opinion.
https://hg.mozilla.org/integration/mozilla-inbound/rev/757a48403154
https://hg.mozilla.org/mozilla-central/rev/757a48403154
Comment on attachment 583421 [details] [diff] [review] Patch [Approval Request Comment] Cleans up the code, Uses a better pattern. Blocking other changes from Aurora.
Comment on attachment 583421 [details] [diff] [review] Patch [Triage Comment] Mobile only - approved for aurora.
https://hg.mozilla.org/releases/mozilla-aurora/rev/ac659ffd7c54
or
