I'm not sure if I spoke too soon.
Before that changeset, the chrome.manifest was telling the compose
window to load a liberator.xul that didn't exist. That changeset tells
it to start loading the correct liberator.xul.
So the reason why that changeset "breaks" the compose window is because
it finally turns liberator *ON*.
I thought I went back far enough. Are you saying that once upon a time
the compose window properly loaded liberator.xul *AND* respected the tab
command? For now, it appears like the reason why tab is "broken" in the
compose window is because it is behaving exactly as it would in a web
browser.
I'll see if I can find a changeset even farther back that has liberator
turned on within the compose window /and/ has tab keys working properly.
--Ted
On 12/16/08 10:35 AM, Ted Pavlic wrote:
Result of git bisect:
ea2111c4b4b60d010232105a41ba9862b3947df4 is first bad commit
commit ea2111c4b4b60d010232105a41ba9862b3947df4
Author: Martin Stubenschrott<[email protected]>
Date: Wed Dec 3 00:31:29 2008 +0100
fixed muttator's chrome.manifest
:040000 040000 c6bd7a9cbe6b27adf1cdffd6193a15337f753fc4
c19311e1b08134333b570714ddb5c1dc84aba504 M muttator
I haven't looked into it more than that.
--Ted
On 12/12/08 8:30 PM, Martin Stubenschrott wrote:
On 2008-12-12 15:55, Ted Pavlic wrote:
In the compose window, "Tab" used to insert a tab. Now I hit tab and
"[No Name]" gets highlighted in the status line.
What happened to tab? How to get it back? :)
I noticed it is broken, just didnt have time to fix it. I think
it broke when doing some changes to the selection controller, but
i might be wrong. At least it's broken for a few weeks now, not just
yesterday. It would be cool, if you could git bisect the problem.
--
Martin
_______________________________________________
Muttator mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/muttator
--
Ted Pavlic <[email protected]>
_______________________________________________
Muttator mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/muttator
