Hi Patrick,

Could you explain what your SFDateInput extension does? The general approach when using jQuery, which I've tried to get SF to follow, is to use classes instead of IDs whenever possible - it leads to significantly simpler code. Is it possible that your extension could do the same thing?

-Yaron

On Mon, Jan 17, 2011 at 3:58 AM, Patrick Nagel <mail@patrick-nagel.net> wrote:
Hi,

today I updated from SF 1.9.1 to 2.0.8, and found my custom SFDateInput
enhancement extension to be no longer working.
Since the extension provides JavaScript to fill in Year/Month/Day with
one click, it requires the year/month/day fields to have IDs. The
attached patch to SF (r80431) re-introduces IDs to year/month/day fields.

I didn't add IDs to hh/mm/ss, but maybe that's also a good idea. Also,
maybe the $input_id parameter to monthDropdownHTML() should be moved to
the left, for consistency, but I didn't want to break any other
(possible) code that calls monthDropdownHTML().

Patrick.

--
Key ID: 0x86E346D4 http://patrick-nagel.net/key.asc
Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel




--
WikiWorks MediaWiki Consulting http://wikiworks.com