<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Setting value of calcite-input-number does not work if value is a number in Calcite Design System Questions</title>
    <link>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1592846#M813</link>
    <description>&lt;P&gt;Hey &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/39681"&gt;@ChristopheSuter&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I see what you mean, I started in version 2.13 and had this issue as well, after upgrading last week to 3.0.3, it still continues, I'd assume this will be the case for the time being until it is changed, I found the GitHub page for it, and see if I can raise an issue if I figure out what could be causing it!&lt;/P&gt;&lt;P&gt;Cody&lt;/P&gt;</description>
    <pubDate>Thu, 06 Mar 2025 17:22:12 GMT</pubDate>
    <dc:creator>CodyPatterson</dc:creator>
    <dc:date>2025-03-06T17:22:12Z</dc:date>
    <item>
      <title>Setting value of calcite-input-number does not work if value is a number</title>
      <link>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1592772#M810</link>
      <description>&lt;P&gt;Setting the value of a calcite-input-number does work only if value is a string&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;See:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://codepen.io/christophesuter/pen/YPzQXRz?editors=1011" target="_blank"&gt;https://codepen.io/christophesuter/pen/YPzQXRz?editors=1011&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if changing the code&amp;nbsp;input.value=23 to&amp;nbsp;input.value='23' it works&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is this the expected behavior for the future versions ? If not, does anyone have a workaround for this ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 15:29:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1592772#M810</guid>
      <dc:creator>ChristopheSuter</dc:creator>
      <dc:date>2025-03-06T15:29:18Z</dc:date>
    </item>
    <item>
      <title>Re: Setting value of calcite-input-number does not work if value is a number</title>
      <link>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1592793#M811</link>
      <description>&lt;P&gt;Hey &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/39681"&gt;@ChristopheSuter&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've noticed this as well when working in Calcite, but I haven't found a guaranteed fix other than converting the value to a string when it's assigned. I used String(variable) and it dynamically converts it for me. I experimented a bit with your CodePen, but it seems it must be normal.&lt;/P&gt;&lt;P&gt;Cody&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 16:18:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1592793#M811</guid>
      <dc:creator>CodyPatterson</dc:creator>
      <dc:date>2025-03-06T16:18:21Z</dc:date>
    </item>
    <item>
      <title>Re: Setting value of calcite-input-number does not work if value is a number</title>
      <link>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1592828#M812</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/712076"&gt;@CodyPatterson&lt;/a&gt;, basically I have migrated the Core API, so I jumped from&amp;nbsp;&lt;SPAN&gt;2.10.1 to 3.0.3 and this was not the case before... just wanted to know if converting all to string was mandatory now ..&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 17:00:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1592828#M812</guid>
      <dc:creator>ChristopheSuter</dc:creator>
      <dc:date>2025-03-06T17:00:25Z</dc:date>
    </item>
    <item>
      <title>Re: Setting value of calcite-input-number does not work if value is a number</title>
      <link>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1592846#M813</link>
      <description>&lt;P&gt;Hey &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/39681"&gt;@ChristopheSuter&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I see what you mean, I started in version 2.13 and had this issue as well, after upgrading last week to 3.0.3, it still continues, I'd assume this will be the case for the time being until it is changed, I found the GitHub page for it, and see if I can raise an issue if I figure out what could be causing it!&lt;/P&gt;&lt;P&gt;Cody&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 17:22:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1592846#M813</guid>
      <dc:creator>CodyPatterson</dc:creator>
      <dc:date>2025-03-06T17:22:12Z</dc:date>
    </item>
    <item>
      <title>Re: Setting value of calcite-input-number does not work if value is a number</title>
      <link>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1593484#M814</link>
      <description>&lt;P&gt;Hey Christophe,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Yes this is expected and is the intended behavior going forward. The is in line with the native input element where the `value` is always a string.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2025 18:16:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/calcite-design-system-questions/setting-value-of-calcite-input-number-does-not/m-p/1593484#M814</guid>
      <dc:creator>DitwanDPrice</dc:creator>
      <dc:date>2025-03-07T18:16:22Z</dc:date>
    </item>
  </channel>
</rss>

