JS Errors on date pickers

Description

Using Ortus DataBoss Standalone v2.2.0+00038 as well as Ortus DataBoss Standalone v2.2.0+00046 as a module within a ColdBox 4.x app

On every page in DataBoss I'm getting the following Javascript errors in the Chrome console:

Additionally the date and time pickers don't display properly when you annotate your properties as below with db_html="datetime":

property name="createdAt" column="CreatedAt" ormtype="timestamp" db_html="datetime"; property name="updatedAt" column="UpdatedAt" ormtype="timestamp" db_html="datetime";

These fields in the SQL Server are of type `datetime`.

When you do annotate as above, here are the console errors from within Chrome:

Attachments

2

Gliffy Diagrams

Activity

Luis MajanoMay 26, 2016 at 10:46 PM

You can update it

Luis Majano
CEO
Ortus Solutions, Corp
www.ortussolutions.com
P/F: 1-888-557-8057

On Thu, May 26, 2016 at 8:39 AM -0700, "Gavin Pickin (JIRA)" <jira@ortussolutions.atlassian.net> wrote:

Message Title

Gavin Pickin commented on https://ortussolutions.atlassian.net/browse/DATABOSS-122#icft=DATABOSS-122

 

Re: JS Errors on date pickers

Luis Majano - See my first comment, can we update Rangy, or is that built into one of our components we're using?
That's a blocker on this ticket.

Luis Majano - See pull request for the other change

Add Comment

 

This message was sent by Atlassian JIRA (v1000.5.2#72002-sha1:b4422fe)

Gavin PickinMay 26, 2016 at 3:38 PM

- See my first comment, can we update Rangy, or is that built into one of our components we're using?
That's a blocker on this ticket.

- See pull request for the other change

Gavin PickinMay 10, 2016 at 5:47 AM

I updated onChange triggered function, to check for $.ready() before completing the function. Its a crude fix, but its that, or change the date based onChange text bindings to onReady bindings. I don't like either solution, especially since its only showing in Chrome, that I can tell.

https://bitbucket.org/ortus/databoss/pull-requests/2/updated-onchange-triggered-function-to/diff

Gavin PickinMay 10, 2016 at 5:39 AM

The chrome error 'Discontiguous selection is not supported.' is an issue with Rangy and a non authoritative W3C spec.
According to research, this error is not suppressible... and not fixable.

https://bugs.chromium.org/p/chromium/issues/detail?id=399791

The rangy notes are here
https://github.com/timdown/rangy/issues/247

Can we update rangy? I cannot find the source files for Rangy to determine the version.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Sentry

Created March 21, 2016 at 3:17 PM
Updated September 20, 2018 at 6:39 PM
Resolved May 27, 2016 at 1:34 PM

Flag notifications