#6297 No vertical scroll bar when text is longer than text field in wiki

v1.3.1
closed
Wiki
2015-08-10
2013-05-30
Anonymous
No

Originally created by: brousch

No vertical scroll bar when text is longer than text entry field. In the attachment, there are several more lines below "Other Ideas". Using Google Chrome Version 27.0.1453.93 on Kubuntu 12.04.

1 Attachments

Related

Tickets: #7827

Discussion

  • Dave Brondsema

    Dave Brondsema - 2013-05-30
    • labels: --> ux
    • Milestone: limbo --> forge-backlog
     
  • Dave Brondsema

    Dave Brondsema - 2013-05-30

    Confirmed in Chrome/OSX (using page https://sourceforge.net/p/varmintpi/wiki/Home/edit) FF/OSX is okay.

     
  • Dave Brondsema

    Dave Brondsema - 2014-12-15
    • labels: ux --> ux, sf-current
    • Description has changed:

    Diff:

     
  • Dave Brondsema

    Dave Brondsema - 2014-12-15
    • labels: ux, sf-current --> ux, sf-current, sf-2
     
  • Igor Bondarenko - 2015-01-09
    • Owner: Anonymous --> Igor Bondarenko
    • Labels: ux, sf-current, sf-2 --> 42cc, ux, sf-2, sf-current
    • Status: open --> in-progress
     
  • Igor Bondarenko - 2015-02-05

    Ok, here is what I found:

    • we're using http://www.jacklmoore.com/autosize/ and jQuery 1.8
    • newest version of plugin supports jQuery 1.7+, but it still does not work correctly in this particular case with jQuery 1.8
    • it works perfectly well if we use jQuery 1.9+ with it

    .

    I've tried a bunch of other plugins as a replacements, but all of them had all kinds of problems and I did not want to spend to much time on it. Some of them seem not maintained at all. I've tried:

    .

    Anyway, autosize seems most mature and maintained.

    So, we might want to update jQuery to latest version (we'll need to do this someday anyway, right?). If I understood correctly:

    • breaking changes present only in 1.9, so we can upgrade to 1.11 at once
    • for 1.8 -> 1.9 they have a migration guide and helper plugin for easier transition
    • 2.1 is identical to 1.11, but with no IE 6-8 support, so if we don't need those we can upgrade to 2.1
    • probably, most problematic migration will be for third-party plugins, if they don't have updated version

    .

    What do you think?

     

    Last edit: Igor Bondarenko 2015-02-05
    • Dave Brondsema

      Dave Brondsema - 2015-02-06

      Yeah I think upgrading jquery makes sense, it'd be good to do in general anyway. Want to make a new ticket for that and start looking into that?

       
      • Igor Bondarenko - 2015-02-06

        Do we need IE 6-8 support? If not we can upgrade to 2.x, I guess.

        Created [#7827] and corresponding ticket on 42cc side.

         

        Related

        Tickets: #7827

        • Dave Brondsema

          Dave Brondsema - 2015-02-06

          On SourceForge at least there's still enough IE 8 traffic that I'd like to support that if we can.

           
          • Igor Bondarenko - 2015-02-06

            Yep, 1.x branch is pretty much the same as 2.x, but with support for IE8, so I'll update to latest 1.x.

             
  • Igor Bondarenko - 2015-02-06
    • status: in-progress --> blocked
     
  • Dave Brondsema

    Dave Brondsema - 2015-02-24
    • status: blocked --> closed
    • Reviewer: Dave Brondsema
     
  • Dave Brondsema

    Dave Brondsema - 2015-03-09
    • labels: 42cc, ux, sf-2, sf-current --> 42cc, ux, sf-2
     
  • Dave Brondsema

    Dave Brondsema - 2015-08-10
    • Milestone: unreleased --> v1.3.1
     

Log in to post a comment.