Paolo Amadini schrieb:
On 8/30/2014 2:18 PM, Philip Chee wrote:
SeaMonkey uses Form History:
http://hg.mozilla.org/mozilla-central/rev/f69c9019e0b0
Thanks for the reference! I'll keep in mind that these Form History
interfaces are used by SeaMonkey as well.
I think that any application doing
On 8/30/2014 2:18 PM, Philip Chee wrote:
> SeaMonkey uses Form History:
> http://hg.mozilla.org/mozilla-central/rev/f69c9019e0b0
Thanks for the reference! I'll keep in mind that these Form History
interfaces are used by SeaMonkey as well.
From what I see in the patch above, it seems that this wa
On 15/08/2014 19:55, Paolo Amadini wrote:
> In fact, a search on the mozilla-central [2] and comm-central [3]
> repositories shows that this shared autocomplete code is only used on
> Desktop by Firefox and Thunderbird, while SeaMonkey uses the older XPFE
> autocomplete. Other Toolkit components l
On 8/27/2014 9:50 PM, Neil wrote:
>> The first changes to autocomplete will land in the next few weeks.
>>
> So do you have some bug numbers you can quote us?
You may want to follow bug 951624 at the moment, though the first
interface changes might appear in newly filed dependent bugs. Probably,
n
Paolo Amadini wrote:
The first changes to autocomplete will land in the next few weeks.
So do you have some bug numbers you can quote us?
--
Warning: May contain traces of nuts.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://
On 8/25/2014 12:56 PM, Mark Banner wrote:
> So if I understand you right, we could switch to UnifiedComplete if we
> want to maintain multiple search sources (whilst using toolkit code)?
UnifiedComplete.js is the Places component that allowed us to replace
the autocompletesearch="urlinline history
On 15/08/2014 12:55, Paolo Amadini wrote:
The major change would be the removal of the multiple search sources
from the autocomplete code, since this feature is used heavily by
Thunderbird. For Firefox, we already developed the UnifiedComplete
component that replaces the multiple searches in the
Paolo Amadini wrote:
On 8/15/2014 3:27 PM, Neil wrote:
*SeaMonkey's search bar uses toolkit's autocomplete widget but SeaMonkey's
popup.
You're saying that it manually binds to Toolkit's autocomplete.xml?
Indeed,
http://mxr.mozilla.org/comm-central/source/suite/common/search/search.
On 8/15/2014 3:27 PM, Neil wrote:
>> It soon became apparent that most of the autocomplete code was
>> designed for synchronous operation
>>
> Synchronous operation of what? Autocomplete works like this: You ask for
> some results; some time later, you get some results. How could that be
> less syn
Paolo Amadini wrote:
It soon became apparent that most of the autocomplete code was designed for
synchronous operation
Synchronous operation of what? Autocomplete works like this: You ask for
some results; some time later, you get some results. How could that be
less synchronous?
In fact,
please note that followups are set to m.dev.platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
please note that followups are set to m.dev.platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
As part of a renewed effort to improve the user experience of location
bar searches in Firefox, we have been working on the shared code
handling search-as-you-type in textboxes [1], which is located in Toolkit.
*Current issues*
It soon became apparent that most of the autocomplete code was design
13 matches
Mail list logo
