I created a 7.x version of this module today (actually before I found this module!) that already uses jQuery Placeholder support, which looks like it was also suggested in #1161384: jQuery Placeholder Support. It uses libraries API too, to manage the jQuery-Placeholder dep.

What do you say? :)

(I know 'needs review' is the wrong status, but I couldn't resist).

Comments

bleen’s picture

Status: Needs review » Postponed (maintainer needs more info)

As long as you agree that the goal of this module is only to backfill browser compatibility for those browsers that do not support the HTML5 "placeholder" property then I am ok with this.

Sound ok?

(FYI: needs review is actually the correct status)

damiankloip’s picture

Yes, that sounds fine to me :)

Following in the steps on the 6.x module; providing the element '#placeholder' key and the processing to add the placeholder library.

'Needs review' should usually only be used when a patch is present I think ....

damiankloip’s picture

Status: Postponed (maintainer needs more info) » Active

Let's go with active.

bleen’s picture

Status: Active » Fixed

by the power vested in me....

damiankloip’s picture

Status: Fixed » Active

Not sure if I have any commit access yet? You can review some code first it you like, I don't mind :)

bleen’s picture

You do have access ... just make sure you use the issue queue normally before committing anything. Give people (including me) some opportunity to comment on patches before you commit them. If no one responds after a few days then go for it...

damiankloip’s picture

No fear, Normal issue queue procedure.

It looks like I don't have commit access, on version control, I don't have the maintainer info on there.

bleen’s picture

try now

damiankloip’s picture

Status: Active » Fixed

Perfect :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.