[wp-hackers] JavaScript bugs

[Dobromir Yordanov]

Ah, yes! That's exactly what I needed, I did not realize there is a separate debug setting precisely for JS debugging. That article also looks interesting... Thanks a lot, I'll make sure to look into it more today. 

Sent via iPhone

~Dobri

On Dec 16, 2012, at 1:00 AM, Aaron Jorbin <aaron at jorb.in> wrote:

> Also, make sure you have SCRIPT_DEBUG[1] enabled, especially if you are
> going to be contributing fixes back to WordPress.
> 
> 1) http://codex.wordpress.org/Debugging_in_WordPress#SCRIPT_DEBUG
> 
> http://aaron.jorb.in
> twitter: twitter.com/aaronjorbin
> 
> 
> 
> On Sat, Dec 15, 2012 at 11:33 PM, Drew <xoodrew at gmail.com> wrote:
> 
>> Well since you asked, there's a brand-new Codex article for just such a
>> thing.
>> 
>> http://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors
>> 
>> It has directions for identifying JavaScript errors in the top 5 browsers.
>> 
>> Drew
>> 
>> 
>> On Sat, Dec 15, 2012 at 7:27 PM, William P. Davis <will.davis at gmail.com
>>> wrote:
>> 
>>> Chrome dev tools are fantastic for this as well - better than Firebug,
>> I'd
>>> say. Both will give you the line number in the script where the failure
>>> occurred, and at least Chrome allows you to click on that to be taken
>>> directly to the error.
>>> Sent from my BlackBerry
>>> 
>>> -----Original Message-----
>>> From: Daniel Fenn <danielx386 at gmail.com>
>>> Sender: wp-hackers-bounces at lists.automattic.com
>>> Date: Sun, 16 Dec 2012 13:21:43
>>> To: <wp-hackers at lists.automattic.com>
>>> Reply-To: wp-hackers at lists.automattic.com
>>> Subject: Re: [wp-hackers] JavaScript bugs
>>> 
>>> Hi there,
>>> 
>>> I don't know if you tried this but if you got firefox installed, you may
>>> want to look at firebug[1].
>>> 
>>> Also if you think that there may be some caching going on, I would try
>>> pressing Ctrl F5 to do a force refresh..
>>> 
>>> 
>>> [1] https://addons.mozilla.org/en-US/firefox/addon/firebug/
>>> 
>>> Regards,
>>> Daniel Fenn
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Sun, Dec 16, 2012 at 1:13 PM, Dobromir Yordanov <dyordan1 at ramapo.edu
>>>> wrote:
>>> 
>>>> Hey guys and gals,
>>>> 
>>>> Anyone know of a good way to find out what JS function is responsible
>> for
>>>> a certain behavior other than going through the JS files and trying to
>>>> guess? I'm trying to patch up some JS bugs on Wordpress and it seems a
>>> bit
>>>> trickier than PHP patching. Also, whatever I change doesn't seem to be
>>>> reflected when I reload so I'm guessing some caching kicks in (other
>> than
>>>> my browser's which should be disabled). Any ideas how to get around
>> that?
>>>> Thanks!
>>>> 
>>>> ~Dobri
>>>> _______________________________________________
>>>> wp-hackers mailing list
>>>> wp-hackers at lists.automattic.com
>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers