v4.33, bug...search component will disappear ( height = 0px ) if you don't use calcite component.
while V4.32, search component don't tie to calcite component.
all other component works fine, except Search component tie to calcite in v4.33.
here is sample if you have v4.33 with calcite, search is fine
If you comment out calcite, search box is gone, ( height: 0px )
Solved! Go to Solution.
Hi @hoogw ,
Calcite is a dependency for the map components. We have built the map components using Calcite so you will need to include it as a dependency for things to work correctly. It was working previously because Search wasn't fully refactored from a widget to a web component.
https://developers.arcgis.com/javascript/latest/get-started/#setup
when esri can fix this bug? I don' t use third party CSS style like calcite. It is bad idea to use third party CSS, like calcite. Even calcite is ESRI's stuff, but still 3rd party CSS. still bad idea. calcite make every one wearing same cloth with esri-logo, horrible idea. When you walk on street, you see everyone wear esri-logo T-shirt, that is what calcite does. Horrible idea.
here is v4.32, comment out calcite, search box is fine.
I want esri do fix the same for v4.33
Hi @hoogw ,
Calcite is a dependency for the map components. We have built the map components using Calcite so you will need to include it as a dependency for things to work correctly. It was working previously because Search wasn't fully refactored from a widget to a web component.
https://developers.arcgis.com/javascript/latest/get-started/#setup
@Sage_Wall not quite true.
map component and basemap-gallery component should be already be refactored from widget to component. Why these 2 dont' depend on calcite? basemap-toggle component also does not depends on calcite, why only search component depends on calcite?
Do you know 2nd component like search component, depends on calcite on v4.33, not on v4.32?
search component on v4.33 without calcite has height:0px, this is obviously is a bug. Even calcite fix this bug, but does not means this bug is already self fixed.
Without calcite on v4.33, all other component works fine. web component should not depends on any 3rd party CSS style( such as calcite ).
I could look into it further, but `@arcgis/core` also imports specific calcite components. Not the whole library, but only the specific calcite components that are used by the widgets. Some of the web components may continue to work without adding calcite directly as a dependency because those same calcite components are included with core. This isn't very reliable though and moving forward fewer calcite imports will be happening in the core api as widgets are deprecated and refactored to be components. Print is an example of another component that will fail to work without importing calcite as a dependency.
https://codepen.io/sagewall/pen/ZYGwWJM
Yes, print component is dependent on calcite on both 4.32, and 4.33.
That is very bad idea, horrible idea.
We as user, need your web component as pure as any html tag element. ( no CSS style at all )
We as user will apply our CSS style or not as our will after.
Now your guys just poluted with 3rd-party calcite (esri-flavored-logo-ed), calcite is disgusting like a uniform. Calcite is like esri-branded-uniform, we as owner of our product is sick of esri-logo-ed-uniform.
we are our map's owner, we want to wear what ever color we like, walmart is blue, hom-depot is orange,
target is red, best-buy is yellow and blue, etc....
and now you guys just polute it with disgusting calcite.
We as user, map owner want you make component as style independent. No-style like any other regular html-tag. We don't need you to esri-branded....
https://codepen.io/sagewall/pen/ZYGwWJM?editors=1000