Ticket #7110 (closed bug: invalid)

Opened 2 years ago

Last modified 7 months ago

Multiple calls to effect.scale should be based on the original %

Reported by: gnarf Owned by: gnarf
Priority: minor Milestone: 1.10.0
Component: ui.effects.* (individual effect) Version: 1.8.10
Keywords: Cc:
Blocking: Blocked by:

Description

Currently, calling scale twice on an element, if you want it to grow to 150% then back to 100% you need to do this:

$("#element").effect("scale", { percent: 150 }, 1000).effect("scale", { percent: 66 }, 1000)

The second call to scale should state percent: 100 IMO

Change History

comment:1 Changed 2 years ago by scott.gonzalez

The problem I see with this is that any changes made by the user between the two calls to scale will be ignored.

comment:2 Changed 2 years ago by gnarf

Not necessarily - we could use .data() to store the current "percent" of the element along with some meta-information, perhaps also detecting any changes made to the properties after our animation completed before recalculating the new values...

comment:3 Changed 9 months ago by scott.gonzalez

@gnarf is this a duplicate of #7041?

comment:4 Changed 7 months ago by scott.gonzalez

  • Milestone changed from 1.9.0 to 1.10.0

comment:5 Changed 7 months ago by mikesherov

  • Owner set to gnarf
  • Status changed from new to pending

I'm fairly certain this is a dupe of #7041 as scott mentions. gnarf, any thoughts? I'm returning to pending so trac-o-bot can deal with this if you don't respond :-)

comment:6 Changed 7 months ago by trac-o-bot

  • Status changed from pending to closed
  • Resolution set to invalid

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.