Will the API in bug 1460412 have an option to chose the focus behaviour (address bar vs. content)? There are use cases for both behaviours. And when will this API be implemented? ni? for this question. > The current behavior was introduced in June 2018 and has been the default for nearly seven months. If you want to say that it's not bad because there were no reports since June 2018: That's my fault because I didn't redirected the bug reports to Mozilla. I got all the bug reports because for the users of New Tab Override it's a bug of New Tab Override, not a bug of Firefox. I got reports via Github, e-mails, AMO reviews and my social media channels. And I got these reports since early in July 2018. It was not possible for me to investigate the issue earlier for unrelated reasons. > Looking at the stats for New Tab Override, the number of users and downloads has remained steady for the past six months. The number of downloads doesn't matter, the number of users is important. The number of users dropped from ~ 125,000 to 102,000 between june and today. That's not "steady" at all. In May 2018 New Tab Override even had ~130,000 users but then Firefox 60 was released which broke another feature of New Tab Override (open about:blank in a new tab) and I had to implement a bad workaround (This workaround also stopped to work with Firefox 61 so it's another feature I had to drop and a change which was not announced to add-on developers! Yes, it's possible now without an add-on at all but for users of New Tab Override Firefox was broken because of that!). > but the data shows it hasn't impacted usage of the extension Sorry, but to lose 30,000 users in a few months is a significant (!) loss of users for an add-on with "only" ~ 130,000 users…
Bug 1516777 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Will the API in bug 1460412 have an option to chose the focus behaviour (address bar vs. content)? There are use cases for both behaviours. And when will this API be implemented? ni? for this question. > The current behavior was introduced in June 2018 and has been the default for nearly seven months. If you want to say that it's not bad because there were no reports since June 2018: That's my fault because I didn't redirected the bug reports to Mozilla. I got all the bug reports because for the users of New Tab Override it's a bug of New Tab Override, not a bug of Firefox. I got reports via Github, e-mails, AMO reviews and my social media channels. And I got these reports since early in July 2018. It was not possible for me to investigate the issue earlier for unrelated reasons. > Looking at the stats for New Tab Override, the number of users and downloads has remained steady for the past six months. The number of downloads doesn't matter, the number of users is important. The number of users dropped from ~ 125,000 to 102,000 between june and today. That's not "steady" at all. In May 2018 New Tab Override even had ~130,000 users but then Firefox 60 was released which broke another feature of New Tab Override (open about:blank in a new tab) and I had to implement a bad workaround. This workaround also stopped to work with Firefox 61 so it's another feature I had to drop because of a change of Firefox. Yes, it's possible now without an add-on at all but for users of New Tab Override Firefox was broken because of that! In the past months there were more than one change in Firefox which all caused trouble for users of New Tab Override. > but the data shows it hasn't impacted usage of the extension Sorry, but to lose 30,000 users in a few months is a significant (!) loss of users for an add-on with "only" ~ 130,000 users…
Will the API in bug 1460412 have an option to chose the focus behaviour (address bar vs. content)? There are use cases for both behaviours. And when will this API be implemented? ni? for these questions. > The current behavior was introduced in June 2018 and has been the default for nearly seven months. If you want to say that it's not bad because there were no reports since June 2018: That's my fault because I didn't redirected the bug reports to Mozilla. I got all the bug reports because for the users of New Tab Override it's a bug of New Tab Override, not a bug of Firefox. I got reports via Github, e-mails, AMO reviews and my social media channels. And I got these reports since early in July 2018. It was not possible for me to investigate the issue earlier for unrelated reasons. > Looking at the stats for New Tab Override, the number of users and downloads has remained steady for the past six months. The number of downloads doesn't matter, the number of users is important. The number of users dropped from ~ 125,000 to 102,000 between june and today. That's not "steady" at all. In May 2018 New Tab Override even had ~130,000 users but then Firefox 60 was released which broke another feature of New Tab Override (open about:blank in a new tab) and I had to implement a bad workaround. This workaround also stopped to work with Firefox 61 so it's another feature I had to drop because of a change of Firefox. Yes, it's possible now without an add-on at all but for users of New Tab Override which used this option Firefox was broken because of that! In the past months there were more than one change in Firefox which all caused trouble for users of New Tab Override. > but the data shows it hasn't impacted usage of the extension Sorry, but to lose 30,000 users in a few months is a significant (!) loss of users for an add-on with "only" ~ 130,000 users…
Will the API in bug 1460412 have an option to chose the focus behaviour (address bar vs. content)? There are use cases for both behaviours. And when will this API be implemented? ni? for these questions. > The current behavior was introduced in June 2018 and has been the default for nearly seven months. If you want to say that it's not bad because there were no reports since June 2018: That's my fault because I didn't redirected the bug reports to Mozilla. I got all the bug reports because for the users of New Tab Override it's a bug of New Tab Override, not a bug of Firefox. I got reports via Github, e-mails, AMO reviews and my social media channels. And I got these reports since early in July 2018. It was not possible for me to investigate the issue earlier for unrelated reasons. > Looking at the stats for New Tab Override, the number of users and downloads has remained steady for the past six months. The number of downloads doesn't matter, the number of users is important. The number of users dropped from ~ 125,000 to 102,000 between june and today. That's not "steady" at all. In May 2018 New Tab Override even had ~130,000 users but then Firefox 60 was released which broke another feature of New Tab Override (open about:blank in a new tab) and I had to implement a bad workaround. This workaround also stopped to work with Firefox 61 so it's another feature I had to drop because of a change of Firefox. Yes, it's possible now without an add-on at all but for users of New Tab Override which used this option Firefox was broken because of that! In the past months there was more than one change in Firefox which caused trouble for users of New Tab Override. > but the data shows it hasn't impacted usage of the extension Sorry, but to lose 30,000 users in a few months is a significant (!) loss of users for an add-on with "only" ~ 130,000 users…
Will the API in bug 1460412 have an option to chose the focus behaviour (address bar vs. content)? There are use cases for both behaviours. And when will this API be implemented? ni? for these questions. > The current behavior was introduced in June 2018 and has been the default for nearly seven months. If you want to say that it's not bad because there were no reports since June 2018: That's my fault because I didn't redirected the bug reports to Mozilla. I got all the bug reports because for the users of New Tab Override it's a bug of New Tab Override, not a bug of Firefox. I got reports via Github, e-mails, AMO reviews and my social media channels. And I got these reports since early in July 2018. It was not possible for me to investigate the issue earlier for unrelated reasons. > Looking at the stats for New Tab Override, the number of users and downloads has remained steady for the past six months. The number of downloads doesn't matter, the number of users is important. The number of users dropped from ~ 125,000 to 102,000 between june and today. That's not "steady" at all. In May 2018 New Tab Override even had ~130,000 users but then Firefox 60 was released which broke another feature of New Tab Override (open about:blank in a new tab) and I had to implement a bad workaround. This workaround also stopped to work with Firefox 61 so it's another feature I had to drop because of a change of Firefox. Yes, it's possible now without an add-on at all but for users of New Tab Override which used this option Firefox was broken because of that! In the past months there was more than one change in Firefox which caused trouble for users of New Tab Override. > but the data shows it hasn't impacted usage of the extension Sorry, but to lose 30,000 users in a few months is a significant (!) loss of users for an add-on with "only" ~ 130,000 users. To say it hasn't impacted usage of the extension is a depressing conclusion for an add-on developer…