Comment 8 for bug 1704873

Bill, do you think we could hold off on more dramatic widget changes for a later branch that makes use of that pattern everywhere (for example, the item editor, which I cribbed from)? I'm sympathetic to any experience of wonkiness.. right now with your branch I get wonkiness of my own with lower window widths, where the Template Apply button squishes next to the Printer selector and tricks me into thinking it doesn't go with templates. I also like the pattern where you can click on the label and have focus jump to the widget, though apparently I didn't do that with this one.

With the Default button, my intention (and it looks like I overlooked this too) was to have the last template applied be sticky and auto-apply on subsequent page loads, to save clicks with repeat workflows. The XUL client is sticky on any field change, though I don't want to go that far. I'm okay with a blank (or even a labelled) menu entry in the Template selector serve the same function as the Default button (though we might would want to disable the Save/Delete buttons for that selection), and any move in this regard is more than the XUL client has, at least, but I think we should have some consistency with other template editing interfaces. What do other folk think?