-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
115 compatibility plan? #39
Comments
I found it funny that ChangeQuote at last had an update on October 2 (although I didn't come see what it was about, also I'm a bit confused that 1.6.1, as Thunderbird reports, isn't mentioned as the latest release here on Github - it says 1.6?)... and then just a day or so later, TB 115 immediately broke it! Probably just a versioning conflict, but yeah Mozilla's model of how it handles addons now (vs. the days when you could fool it by messing about in about:config) is sometimes really disruptive and probably burdensome to developers... |
Agree the update seems to have been almost synchronous. Hopefully it won't be a horrible painful fix due to some capriciously deleted API hook. 115 is feeling like another 78 where the devs decide they know how email is supposed to work and anyone figuring out ways to make it different is not just wrong, but so immorally wrong that they need to be stopped for their own benefit. Each one of these API hook flushes convinces pro-bono devs of really critical plugins that make TB usable for most people at all that it isn't worth it, that they're not appreciated. Mozilla's outreach to the ecosystem is, to say the least, lacking. That no dev, no product manager ever addresses the legitimate horror show of their "upgrades" speaks volumes. But so too does the fact that there's no real alternative. Commercial software is, if anything, even less responsive. And the pressure of "give us all your datas for free email" web services has made useful, privacy preserving, "own your data," email clients a niche product. So, in the end, we'll figure out how to undo and work around the UI/UX/API horrors visited upon us by the uncaring devs in time, as we have many times before. Just frustrating to have to do it again. You'd think they'd have learned from 78, but no.... |
I use CQ 1.6.1 but my TB 115.3.1 (LinuxMint) tells me, CQ is not compatible with it!? Is there a way to enable it again? Tnx in advance. |
I'm working on it, but it takes times because I need to rewrite code due to API changes. |
I'ma gonna guess there was no active outreach from Mozilla to give a critical developer, such as yourself, any input in these API changes or even giving sufficient advance notice and guidance to proactively accommodate them? |
The issue is that I didn't expect such impact |
I have almost done all of the work, a pre-release version 17.0 is available here: |
We're all annoyed at Mozilla here really, not at you! :) |
Indeed, it is Mozilla, not you. We've been through this over and over and it feels almost as if they break API calls not merely capriciously but maliciously. Thank you for your awesome work maintaining truly essential features for a core productivity tool. |
Thanks for the 1.7.0 update. |
The case of forward was not handled, I updated the code to close the window when the option is checked But I confirm there is a bug in the case of reply when standard header option is also checked: the window is not closed. |
Finally I found the bug for the case when option "Close message window after reply or forward " is checked and when "standard Thunderbird reply header" is selected |
Thanks for the very quick updates. I use the standard header option. |
|
That's working great now. Thanks. On a slightly different topic, why are these two options grayed out? "Add a linebreak in text plain headers" Thanks, |
I think there is a bug when initializing the options values, the two options should be available, I will fix it. |
It might be a problem link to the identification of the window to close. In the case of the reply, is the window title name is " |
The window title name of the email I want to forward/reply to is: If I click forward, the new window title name becomes: If I click reply, the new window title name becomes: |
I changed the way I search the window to close in a new version 1.7.5: |
This is working now in version 1.7.5. Thanks! Bill |
1.7.5 is still going wrong in the same way. |
@Duncan-Moore I'm trying to reproduce your problem on my side. |
'Reply header' only has 'Standard Thunderbird reply header' checked. I'm using Windows 10. |
Can you check if there are any error messages in Error console ? Error console can be shown using the shortcut Ctrl+Shift+J or via the Thunderbird tools menu under Developer Tools -> Error Console. |
I've copied and pasted the text from the console window - I wasn't sure if there's a better way to do this. Double clicking the email I want to reply/forward gives: Error: This will be removed. Use :ref: Forwarding the email (which does close the old window) gives: window.controllers/Controllers is deprecated. Do not use it for UA detection. 2 blank Replying to the email (which doesn't close the old window) gives: window.controllers/Controllers is deprecated. Do not use it for UA detection. 2 blank |
I understood the problem, it is the case when there is no default identity configured. |
Yes, that's working. |
Many tnx! Seems to work fine! 👍 |
I just noticed that it works fine in mail messages when I use Reply, but is still broken in Newsgroups when I use Followup. On Thu, Oct 26, 2023, At 01:43 PM, "xxxx" wrote: ([[br) /> My Newsgroup Reply Headers are defined like this: I'm using ChangeQuote version 1.7.6. Bill |
I have released a new version, 1.7.9 the issue for newsgroups should be fixed : |
Working fine now. Thanks @caligraf Bill |
I think I'm seeing a minor bug (unless I'm just doing something wrong). If I set my reply header to "On %%5, %%6 wrote:" my resuling header in the reply has a capital "A" in the word "at" rather than a lower case "a". Example: On Friday, October 27, 2023, At 02:39 PM, caligraf wrote: Thanks, |
I can see as recipients only name now, not address like before... its a bug? It is also somehow possible again recipients as only address? It is possible combination name and address? name Thanks Martin |
it is a bug, I made a fix, here is a new version 1.7.10 @BillH99999 This version also fixes the bug of "A" in uppercase instead of lowercase in reply header |
I can confirm that the "a" is now in lower case. Thanks! |
Great, I see as recipients address now when I use %%2 But sometimes I see only address and sometimes combination name and address, I do not know why not only one or second option, maybe it is due how Thunderbird show contacts? But anyway I am satisfied 👍 |
115 once again demonstrates TB devs disregard of the developer community and breaks plugins essential to efficient use of the product. I realize this is an endless battle against a truly uncaring project that believes only they know the one true way to do email, but is there any hope of a fix?
The text was updated successfully, but these errors were encountered: