in reply to Re: Message Outbox: "delete" msg box button? (updated)
in thread Message Outbox: "delete" msg box button? (updated)

> "sticky fields".

I think sticky fields are OK as long as it is easy to reset again. That's very convenient for mobile users without CUA shortcuts.

I wrote and tested some JS code yesterday to show a reset button behind each text field. (Of course only shown if JS is enabled)

I could add a patch today, my concern is testing.

After reading the pmdev wiki and the  Pmdev HowTo Wiki I'm not sure how to safely test and discuss a working copy of that node.

Do pmdevs patch directly into production?

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

  • Comment on Re^2: Message Outbox: "delete" msg box button? (dev cycle?)

Replies are listed 'Best First'.
Re^3: Message Outbox: "delete" msg box button? (dev cycle?)
by Corion (Patriarch) on Jan 03, 2016 at 17:52 UTC

    Yes, at least until we get a separate testing instance back up again (which I foresee only after a move to git or whatever). Testing in production isn't that bad here IMO, as the risks are low and usually people stick around until they're convinced that their change actually works :)

[reply]
      OK thanks.

      some questions:

      1. Is it OK if I implement a JS solution here?

      2. Which CGI version does PM use?

      3. Is it possible to clone/fork a node for testing? (Of course overkill here, just in theory)

      Cheers Rolf
      (addicted to the Perl Programming Language and ☆☆☆☆ :)
      Je suis Charlie!

[reply]

        As long as the site still works without Javascript (which I assume for this form), Javascript is OK. I just don't like to encourage leaving Javascript switched on, as I think it's bad security practice.

        For CGI.pm , I'd have to look. I assume it's a 3.x version, likely patched locally.

        It's easy to copy a node, but that node stays around forever.

[reply]

In Section Perl Monks Discussion