search

vessillo / foxreplace

Automatically exported from code.google.com/p/foxreplace
0 stars 0 forks source link

Auto-replace on page load is not working with content loaded with AJAX #13

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Great addon

but Auto-replace on page load is not working, I have to press on F2 even
when Auto-replace on page load is marked. Tested on several systems
inculding windows and linux workstaions, and it is the same

thank you

Original issue reported on code.google.com by ahmad.ha...@gmail.com on 2 Jun 2009 at 9:57

GoogleCodeExporter commented 9 years ago 
Hi, it works for me. Can you tell me more details? Does it fail with a specific 
URL
or substitution list? Which version are you using?

Original comment by marc.r...@gmail.com on 2 Jun 2009 at 10:22

GoogleCodeExporter commented 9 years ago 
it fails to Auto-replace the local URLs, for example :
file:///media/disk1/file1

won't be replaced except I press F2, Auto-replacement is not working with such 
URLs

I use the latest release

thanks

Original comment by ahmad.ha...@gmail.com on 3 Jun 2009 at 6:04

GoogleCodeExporter commented 9 years ago 
I have tried with a local URL and it works for me. Can you try something? Go to
about:config and look for the preference 
extensions.foxreplace.autoReplaceOnLoad, and
look if it's true or false, then tell me.

Original comment by marc.r...@gmail.com on 3 Jun 2009 at 10:25

GoogleCodeExporter commented 9 years ago 
it is true, and not working

I am using latest firefox 3.0.10 and latest FoxReplace and the platforms are 
Ubuntu,
xp, win7 and vista

Original comment by ahmad.ha...@gmail.com on 6 Jun 2009 at 5:34

GoogleCodeExporter commented 9 years ago 
There is somthing that could be the key to solve the problem. The page that I 
want
the autoreplace to work in it is using the javascript to change the content 
without
changing the URL, maybe this will help

and here is an attachment of the web interface where autoreplace fails

Original comment by ahmad.ha...@gmail.com on 6 Jun 2009 at 5:41

Attachments:

GoogleCodeExporter commented 9 years ago 
Ok, yes, this is the problem. FoxReplace doesn't work automatically with content
loaded or created with JavaScript, because the auto-replace is triggered by the 
load
event.

I will look into this in the future.

Original comment by marc.r...@gmail.com on 7 Jun 2009 at 12:11

GoogleCodeExporter commented 9 years ago 
can we expect a solution for that within two months ? or you are planning for a
longer time ?

thanks for your efforts

Original comment by ahmad.ha...@gmail.com on 7 Jun 2009 at 7:29

GoogleCodeExporter commented 9 years ago 
Probably not, because I have to do other things first, and then I will have to
investigate how to do this (i.e. look what events are generated when the 
content is
modified with JavaScript and how to apply the substitutions only to the changed 
part).

Original comment by marc.r...@gmail.com on 8 Jun 2009 at 10:17

GoogleCodeExporter commented 9 years ago 
I assume this would be the problem causing this not to work on gmail pages?  
Because
that is really where I wanted this to work :)

Original comment by phili...@gmail.com on 27 Aug 2009 at 4:28

GoogleCodeExporter commented 9 years ago 
Yes, this is the problem with Gmail, but it doesn't have an easy solution that 
I know
yet.

Original comment by marc.r...@gmail.com on 27 Aug 2009 at 12:07

GoogleCodeExporter commented 9 years ago 
    Ever since the recent update, foxreplace has been suffering from serious bugs. first, the substitution list dissapeared and wasnt working properly, now the auto replace fails to work. At first, I actually did went back to version 12. But foxreplace updated itself without even telling me. 
     I didnt realize that fox replace had been updated until i saw that certain words havent been replaced, then thats when i found out that auto replace didnt work, and this is when i found out that foxreplace silently updated itself to version 13. 
   Its probably because the automatic updates was on default, but i thought that there was going to be a box asking me if i wanted to update or not. When i tried to go back to version 12, i couldnt because its not compatible with the current version of firefox. So now i am forced to be the beta tester for this new lousy version of foxreplace. Once foxreplace is fixed, no more will i update it, and i will make sure the automatic updates is set to off.

Original comment by Bluemime...@gmail.com on 14 Jul 2012 at 6:37

GoogleCodeExporter commented 9 years ago 
the package of foxreplace is just a zip file, uncompress your favorite
version and edit the compatibility number and zip it again, wopse ! it
works !

Original comment by ahmad.ha...@gmail.com on 14 Jul 2012 at 7:06

GoogleCodeExporter commented 9 years ago 
And where do i find this package of foxreplace? what is its filename?  Im using 
an imac. i searched on my computer, and i couldnt find the zipfile you are 
talking about.

Original comment by Bluemime...@gmail.com on 14 Jul 2012 at 7:33

GoogleCodeExporter commented 9 years ago 
It is the xpi file, rename it to zip, uncompress, modify the file
install.rdf (the max_version part), compress again as zip, rename again to
xpi, now you got a working old version with the new firefox versions :)

Original comment by ahmad.ha...@gmail.com on 14 Jul 2012 at 8:22

GoogleCodeExporter commented 9 years ago 
this just sounds confusing. i dont feel comfortable messing around with files 
that most likely firefox depends on. i may end up messing up firefox or 
something.

Original comment by Bluemime...@gmail.com on 14 Jul 2012 at 9:25

GoogleCodeExporter commented 9 years ago 
it works with me, if you want send me your xpi and I'll do it for you.

Original comment by ahmad.ha...@gmail.com on 15 Jul 2012 at 4:20

GoogleCodeExporter commented 9 years ago 
Hi Bluemime2012, if the bug you have is with version 0.13.0, it may be the same 
as in issues #70, #71, #72, #73, and #74, which is fixed in version 0.13.1.

If you have found the bug in version 0.13.1 and you didn't have it in previous 
versions, then you should create a new issue because it's not the same case as 
this one.

Original comment by marc.r...@gmail.com on 15 Jul 2012 at 1:46

GoogleCodeExporter commented 9 years ago 
Create a delay of 1 or 2 seconds before applying it to the page, and your app 
will work for Facebook post/comments.

Original comment by xzn...@gmail.com on 25 Apr 2013 at 2:56

GoogleCodeExporter commented 9 years ago 
Issue 116 has been merged into this issue.

Original comment by marc.r...@gmail.com on 1 Jul 2013 at 3:39

GoogleCodeExporter commented 9 years ago

Original comment by marc.r...@gmail.com on 1 Jul 2013 at 3:41

GoogleCodeExporter commented 9 years ago 
Solution ideas:

- 
http://hacks.mozilla.org/2012/05/dom-mutationobserver-reacting-to-dom-changes-wi
thout-killing-browser-performance/
- 
https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver?redirectlocale
=en-US&redirectslug=DOM%2FMutationObserver

Original comment by marc.r...@gmail.com on 8 Jul 2013 at 2:47

GoogleCodeExporter commented 9 years ago 
Any chance of this being resolved? These days this sort of content is very 
common. Even if it's a limited hack solution it would be better than needing to 
apply the changes manually.

Original comment by hugojh...@gmail.com on 17 Feb 2014 at 5:34

GoogleCodeExporter commented 9 years ago 
Yes, I have a planned workaround that will be in the next version.

Original comment by marc.r...@gmail.com on 18 Feb 2014 at 8:43