<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>I think this only makes sense if we’re removing a supported feature, rather than a legacy pref that was included primarily so we could evaluate and tweak changes between Firefox 1.5 and Firefox 2. That it survived for eight years is an unintended consequence of that choice. The last thing I want to do is create even more work for developers to clean this sort of thing up.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>-- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> firefox-dev [mailto:firefox-dev-bounces@mozilla.org] <b>On Behalf Of </b>Eric Shepherd<br><b>Sent:</b> July 31, 2014 4:29 PM<br><b>To:</b> Robert 'Bobby' Zenz; firefox-dev@mozilla.org<br><b>Subject:</b> Re: Do not remove "Remove the browser.tabs.closeButtons pref"<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div id="bloop_customfont"><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>On July 31, 2014 at 4:17:04 PM, Robert 'Bobby' Zenz (<a href="mailto:robert.zenz@bonsaimind.org">robert.zenz@bonsaimind.org</a>) wrote:<o:p></o:p></span></p></div><div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px'><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black'>So would pointing at addons help? At least temporary, yes. The problem<br>is if these addons die and break.<o:p></o:p></span></p></div></blockquote></div><p><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>It would at least ease the transition, and it would usually be a more user-friendly scenario than simply removing the feature without any advice at all.<o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>I don't have any real worry here, just throwing ideas around to see if anything sticks.<o:p></o:p></span></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px'><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black'>What would be a pretty nice solution, in my opinion, if there would a be<br>a cooperation with addon developers who show interest, like the one from<br>CTR.<o:p></o:p></span></p></div></blockquote></div></div><p><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Yeah, that's true. Perhaps that's something the Firefox dev team could coordinate with dev relations on? Let devrel know when a feature is being removed, offer some tips about how an add-on could replace that functionality, and we could share that information with our add-on developer community.<o:p></o:p></span></p><div id="bloop_sign_1406838400815234048"><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>-- <o:p></o:p></span></p><div><p class=MsoNormal style='line-height:15.6pt'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Eric Shepherd<br>Developer Documentation Lead<br><a href="https://developer.mozilla.org/"><b><span style='color:black'>Mozilla Developer Network</span></b></a> <br>Twitter: <a href="http://twitter.com/sheppy"><span style='color:black'>@sheppy</span></a> <br>Blog: <a href="http://www.bitstampede.com/"><span style='color:black'>www.bitstampede.com</span></a><o:p></o:p></span></p></div></div><p><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'><o:p> </o:p></span></p></div></body></html>