Bug Tracker

Modify

Ticket #9356 (closed enhancement: wontfix)

Opened 3 years ago

Last modified 3 years ago

.css method needs callback for handling -webkit-transition...

Reported by: peter.i.ehrlich@… Owned by:
Priority: low Milestone: 1.7
Component: css Version: 1.6.1
Keywords: 1.7-discuss Cc:
Blocking: Blocked by:

Description

as css properties can now in certain cases be time-based, the jquery method should should be a callback function.

Change History

comment:1 Changed 3 years ago by rwaldron

  • Priority changed from undecided to low
  • Status changed from new to open
  • Component changed from unfiled to css

comment:2 Changed 3 years ago by john

  • Keywords 1.7-discuss added

Nominating ticket for 1.7 discussion.

comment:3 Changed 3 years ago by rwaldron

+0, This is an interesting point, but I think it deserves more discussion

comment:4 Changed 3 years ago by jaubourg

-1, No, transitions should be dealt with in animations first, then, and only then, should we consider re-routing .css to .animate when needs be.

comment:5 Changed 3 years ago by timmywil

-1,

comment:6 Changed 3 years ago by paul.irish

+0 I really like this idea but let's explore it via a duck punch before it heads into core.

generally it woud work like this

1) determine support for css transitions at load

2) if support, on every css() call with attached callback, bind to the associated transitionEnd event (or all of them)

2a) if no support, fire callback immediately after style change is made

3) when transitionEnd event fires, fire callback

Some relevant code is here:  https://github.com/Modernizr/Modernizr/blob/cade16/modernizr.js#L1071-1090

Last edited 3 years ago by paul.irish (previous) (diff)

comment:7 Changed 3 years ago by dmethvin

-1, Plugin first.

comment:8 Changed 3 years ago by john

-1, Seems like focusing on improving animate would be better (or having this as a plugin).

comment:9 Changed 3 years ago by ajpiano

-1, Definitely an awesome idea but "plugin first," i.e., we want to see it happening :)

comment:10 Changed 3 years ago by scott.gonzalez

-1

comment:11 Changed 3 years ago by rwaldron

  • Status changed from open to closed
  • Resolution set to wontfix
  • Milestone changed from 1.next to 1.7

Closing per 1.7 roadmap meeting resolution

Please follow the  bug reporting guidlines and use  jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

View

Add a comment

Modify Ticket

Action
as closed
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.