502202 - modifications to search plugin description files don't get picked up on Windows (editing google.xml manually has no impact)

Status: RESOLVED WONTFIX

(Firefox :: Search, defect)

Description

[kinwolf]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)

After installing firefox 3.5 I wanted to change back my default search to www.google.com/ig so I edited google.xml.  Doing so doesn't work anymore as it seem firefox doesn't read that file after it's initial start.  Someone told me to move then delete google.xml, restart firefox(now google isn't avail anymroe) then close firefox, put back the modified google.xml back in the right folder and restart firefox.  That was the only way to make firefox re-read the xml file.  But I can't believe this behavior is wanted.  

Reproducible: Always

Steps to Reproduce:
1.Modify google.xml to change search page
2.put nothing in the search bar and push "enter".
3.Watch and see that the change is never taken into account
Actual Results:  
the change is never taken into account

Expected Results:  
To get the right search page, that is www.google.com/ig

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

What have you changed? Please attach the changed file to this bug.

Comment 2

[kinwolf]

Attachment: google.xml file with changed in it as asked for

Comment 3

[kinwolf]

I attached the file as requested. The only line changed in it is <SearchForm>http://www.google.com/ig</SearchForm>

Comment 4

[:Gavin Sharp [email: [e-mail]]]

Firefox 3.5 stores engine data in a JSON cache and only reloads the data from the XML files if it detects a change.

We check the directory's lastModifiedTime to determine whether to invalidate the cache, but perhaps that isn't set reliably for file modifications on Windows (I thought we'd tested that?).

Comment 5

[Ryan Flint [:rflint] (ping via IRC for reviews)]

Windows only sets the mtime on the parent directory when the file structure within it changes - other platforms do what you'd expect. We decided that the costs of checking each file every time were far too high to support such a rare use case. As a workaround you can move the file around as you did, or delete search.json from the profile directory.