codaxy / cxjs Goto Github PK

Sometimes it makes sense to have sliders that respond to mouse wheel events over them, so maybe put that as an opt-in attribute?

It would be nice to have a desktop like theme with minimum spacing between components (equivalent to the ExtJS classic one).
Developing "Single Page Applications" requires sometimes to display a lot of widgets in a single window, so having compact components is a need.

Remote lookup examples report an error...

Remote lookups do not send query parameter to the controller query method (see Remote LookupField example at http://cx.codaxy.com/v/master/docs/widgets/lookup-fields). This is at least for versions 16.12.8 and 16.12.9, seems to work fine in Fiddle: http://cx.codaxy.com/fiddle/?f=bK8hnm5g

Clear button position could be slightly better too.

Currently, imports are handled like this:
import {TextField} from 'cx/ui/form/TextField';
or
import {TextField} from 'cx/ui/form/';

Using a build step it would be possible to pre-package and offer multiple entries inside the dist folder. These would be app, ui, forms, grid, nav, layout, svg, charts. After that import would look like this:
import {TextField} from 'cx/forms';;
import {NumericAxis, BarGraph} from 'cx/charts';

Pros:

• Rollup could be used to concatenate all files - Babel would not add its overhead into each file
• Babel could be used to transform JSX - the host app would not have to worry about that and could loose { pragma: 'VDOM.createElement' } from the configuration.
• Probably some performance gains

Cons:

• It's non-trivial to implement - some transformation would have to be done to skip and reference imports which belong to the other output file
• Source maps would have to be used to access original files
• It would be difficult to work with non-compat version of Inferno and Inferno's plugin for Babel - that would require a separate build

It would be best to add scrollbar styling as a global rule.

http://cx.codaxy.com/v/master/docs/widgets/month-fields

It appears that dropdown passes the bottom of the viewport!?

Sometimes, only header cell disappear when column visibility is toggled.
http://cx.codaxy.com/fiddle/?f=JeQA73LV

Hi Marko:

Just a small one. When I select General Purpose Widgets > Heading in CxDocs the browser gives an Unknown prop warning on the level tag. Everything seems to be fine but I can't seem to find where this is coming from. Have you seen this before? I basically get it wherever the level tag is used.

It's a fresh local install and I notice it doesn't happen in the online version of the docs.

Cheers,
Dave

Set touch-action: none where needed.

http://cx.codaxy.com/v/master/docs/charts/pie-charts

Enable flags for autocapitalization, autocorrection, autocompletion for TextBox on mobile devices, as described here: https://davidwalsh.name/disable-autocorrect.

Usage case: username input, which should never be autocapitalized.

• Create a separate docs for Inner and Outer Layouts (currently is all listed together under Layouts).
• In Outer Layouts page include additional info and import paths for Content and ContentPlaceholder components.

Upload button in a neat layout makes container div scrollbar to appear (the container has overflow-x: auto), when it should not.

ColorField and DateField widgets do not display a tooltip feedback in case of an invalid input.
Instead, the previous input value is restored silently.

When a multi-value lookup is required, it remains in "invalid" status on blur, even if it contains some values.

Example:
https://cxjs.io/fiddle/?f=DS65c0fX

Custom formatting (Format.register) is not explained in the docs.

$cx-std-field-state-style-map: cx-deep-map-merge($cx-input-state-style-map, ()) !default;

One would expect that adding something to $cx-input-state-style-map would add it to $cx-std-field-state-style-map, but that's not the case.

Maps, when declared, should depend exclusively on Sass variables.

Fiddle: https://cxjs.io/fiddle/?f=jgXLGgu9

On mobile Safari, the placement of a dropdown with many items is somewhat weird (image 1). However, when activating -webkit-overflow-scrolling: touch on a parent container (when it should be scrollable), it becomes completely clipped (image 2). This is now becoming an issue for all sidebars with lookup items within them.

http://cxjs.io/v/master/themes/material/ - Click Backdrop button

Fixed elements inside of a transformed element (scale, translate) are not fixed to the document.

http://stackoverflow.com/questions/26681718/how-to-retain-fixed-positions-of-elements-inside-transformed-elements

We made a recent change so that buttons do not receive focus on mousedown.
On the other side, by default, TextArea relies on blur event to propagate changes.

The problem occurs when the button is clicked while textarea is focused. Focus stays within the textarea and change is not propagated.

All widgets should work out of the box, so either change the defaults so TextArea submits on every input or focus buttons on click.

Animated windows are nice, but backdrops now look weird. The window first shrinks and after that is done the backdrop disappears. Backdrops should be animated too.

is planned?

When the password is autofilled from Chrome, it will not be recognized as filled until you trigger any event (keypress, mouse click) on the page.

When checkboxes are used for row selection, they should not be focusable...

LookupField will not shrink under ~250px, apparently under any circumstances.

See fiddle: https://cxjs.io/fiddle/?f=11utkOVj

Fiddle: https://cxjs.io/fiddle/?f=8mov7n6V

When passing multiple='true' attribute to the Grid widget, it is possible to select multiple rows holding the Ctrl key. Default behavior deselects all other rows if Ctrl key is not down.

Toggle mod would allow multiple rows selection without holding down the Ctrl key.

https://cxjs.io/fiddle/?p=vwyHzOO1

Styled scrollbars override native scrollbars on mobile devices. Should we turn this on only for larger screens?

Is it possible to have entire containers disabled (meaning, all form inputs on the container would be disabled)?

sortDirection:bind does not work.

Do you support infinite scrolling in grids?
In ExtJS it is implemented as a BufferedStore.

Gray is commonly used for disabled state, using it for selection is a bad choice...

Two possibly related NumberField bugs (http://cx.codaxy.com/v/master/docs/widgets/number-fields)

• when using percentage (ps) format, input field does not allow you to type decimal point
• in the Formatted example, it's not possible to enter a 5-digit number like "23456" by individual keystroke succession. Pasting the value and manipulating the cursor manually works fine here, though.

For example,

cx add route dashboard/world

will fail if folder app/routes/dashboard doesn't exists.

The correct behavior would be to create all missing folders.

When the color picker is activated, it is shown as an overlay.
As soon as the mouse is down, the event is propagated and the overlay disappears, preventing finer color adjustment.

The same behavior can be observed on the color picker itself, indicating that the problem is not in the ColorField widget.
As soon as the mouse is down, the color picker loses focus, preventing finer color adjustment.

It seems that Culture.setCulture is broken.

It would be a good idea if we could have throttling/debouncing options for Cx controls (e.g. slider).

Slider does not appear to respect disabled attribute:

Fiddle:
http://cx.codaxy.com/fiddle/?f=Aaoqc6TO

Tooltips look and feel a little strange on mobile devices, but they work very well on desktop. Maybe it makes sense to have some global configuration for tooltips, at least to be able to hide them all.

It should be readily visible where a certain Cx component can be imported from.

Example: PureContainer, subtitle: import {PureContainer} from 'cx/ui'

The problem lies along these lines:

   handleMouseDown(e){
      this.props.handleSelect(e, new Date(e.target.dataset.date));
   }

For selected date of May 11, 2017, e.target.dataset.date is 2017-5-11, which cannot be parsed by Safari (see image below). 2017-05-11 would have worked fine, it seems.