Michał Gołębiowski-Owczarek
Michał Gołębiowski-Owczarek
Thanks for the report. Since the issue is already in 1.12, given limited team resources it's not likely to be fixed by the UI team; see the project status at...
Thanks for the report. The test case is always useful; manually typing code makes the whole process just a bit longer and sometimes this may be enough of a hindrance...
This issue isn't entirely clear and we don't really do more things to `contextmenu` than we do for e.g. `mousedown` so I'm going to close it. If @markelog replies with...
Thanks for the report. This looks like a 1.13 regression as I can't reproduce the behavior on an older version of the website that used 1.12.1: https://web.archive.org/web/20190308021648/https://jqueryui.com/dialog/ It's not just...
@Josh-Reichman Yes, it looks like it was fixed by #1979, see: https://jsfiddle.net/m_gol/Lgnfyuk4/3/ Thanks for the note! The fix will be included in jQuery UI 1.13.3.
Thanks for the report. Since the issue is already in 1.12, given limited team resources it's not likely to be fixed by the UI team; see the project status at...
> I'd rather have a jQuery.css(elem, name, value) setter and jQuery.css(elem, name) getter if we're going to have one, similar to jQuery.data. At least that would give us some consistency...
> Agreed. In this case, I'd rather see us move to what Dave suggested than drop them completely. That works for me as well. EDIT: issue title updated.
This relates to APIs currently undocumented so I assume deferring it to 3.1.0 would be ok?
OK, deferred to 3.1.0. Please revert if you disagree.