intersystems-community / intersystems-community/DeepSeeWeb
Date Range filter is broken in Firefox
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The Date Range filter generates MDX queries with NaN instead of a date in Firefox. It works fine in both Chrome and Edge.
An MDX query generated in Firefox:
{"MDX":"SELECT NON EMPTY [AccessTimeStamp].[H4].[DayMonthYear].Members ON 1 FROM [APPSIGHT_SIPHON_SSOUSAGE] %FILTER NONEMPTYCROSSJOIN(%OR({%OR([AccessTimeStamp].[H4].[DayMonthYear].&[NaN]:&[NaN])}),[AppsName].[H1].[AppsName].&[SSO].%NOT)"}
The MDX query generated in Chrome:
{"MDX":"SELECT NON EMPTY [AccessTimeStamp].[H4].[DayMonthYear].Members ON 1 FROM [APPSIGHT_SIPHON_SSOUSAGE] %FILTER NONEMPTYCROSSJOIN(%OR({%OR([AccessTimeStamp].[H4].[DayMonthYear].&[67621]:&[67802])}),[AppsName].[H1].[AppsName].&[SSO].%NOT)"}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Date Range filter in Firefox and trace where its date values become NaN before the MDX query is generated. Compare the Firefox query with the working Chrome and Edge output shown in the issue; done means Firefox emits numeric date values instead of NaN while the other browsers continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100