@xapp/form-widget 1.101.0 → 1.103.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Binary file
Binary file
@@ -0,0 +1 @@
1
+ export {};
Binary file
@@ -1,3 +1,20 @@
1
+ /**
2
+ * The phone breakpoint.
3
+ *
4
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
5
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
6
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
7
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
8
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
9
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
10
+ *
11
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
12
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
13
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
14
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
15
+ *
16
+ * Use this instead of writing the query by hand, so the definition lives in one place.
17
+ */
1
18
  .ModalDialog-module_xapp_search_modal__WpGiJ {
2
19
  position: fixed;
3
20
  top: 0;
@@ -10,12 +27,12 @@
10
27
  padding: 48px;
11
28
  z-index: 15000;
12
29
  }
13
- @media (max-width: 640px) {
30
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
14
31
  .ModalDialog-module_xapp_search_modal__WpGiJ {
15
32
  padding: env(safe-area-inset-top) env(safe-area-inset-right) max(env(safe-area-inset-bottom), var(--xapp-keyboard-inset, 0px)) env(safe-area-inset-left);
16
33
  }
17
34
  }
18
- @media (max-height: 640px) and (min-width: 641px) {
35
+ @media (max-height: 640px) and (min-width: 641px) and (pointer: fine) {
19
36
  .ModalDialog-module_xapp_search_modal__WpGiJ {
20
37
  padding-bottom: 24px;
21
38
  }
@@ -37,7 +54,7 @@
37
54
  display: flex;
38
55
  flex-direction: column;
39
56
  }
40
- @media (max-width: 640px) {
57
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
41
58
  .ModalDialog-module_xapp_search_modal__body__qK17C {
42
59
  width: 100%;
43
60
  height: 100%;
@@ -46,6 +63,23 @@
46
63
  .SearchResponseBubble-module_xapp_search_response_bubble__UtmuK {
47
64
  --xapp-bubble-background: #fff;
48
65
  }
66
+ /**
67
+ * The phone breakpoint.
68
+ *
69
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
70
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
71
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
72
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
73
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
74
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
75
+ *
76
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
77
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
78
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
79
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
80
+ *
81
+ * Use this instead of writing the query by hand, so the definition lives in one place.
82
+ */
49
83
  .Card-module_xapp_search_card__9iVCv {
50
84
  border: solid 0 var(--xapp-form-widget-border-color, #d3d3df);
51
85
  border-radius: 12px;
@@ -221,6 +255,23 @@
221
255
  .Carousel-module_xapp_search_carousel__content__EoqyB {
222
256
  flex-grow: 1;
223
257
  }
258
+ /**
259
+ * The phone breakpoint.
260
+ *
261
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
262
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
263
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
264
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
265
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
266
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
267
+ *
268
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
269
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
270
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
271
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
272
+ *
273
+ * Use this instead of writing the query by hand, so the definition lives in one place.
274
+ */
224
275
  .CarouselItem-module_xapp_search_carousel_item__xNpwo {
225
276
  display: inline-flex;
226
277
  flex-direction: column;
@@ -231,7 +282,7 @@
231
282
  .CarouselItem-module_xapp_search_carousel_item__xNpwo:last-child {
232
283
  padding-right: 0;
233
284
  }
234
- @media (max-width: 640px) {
285
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
235
286
  .CarouselItem-module_xapp_search_carousel_item__xNpwo {
236
287
  min-width: 100%;
237
288
  max-width: 100%;
@@ -241,6 +292,23 @@
241
292
  display: flex;
242
293
  flex-direction: column;
243
294
  }
295
+ /**
296
+ * The phone breakpoint.
297
+ *
298
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
299
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
300
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
301
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
302
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
303
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
304
+ *
305
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
306
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
307
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
308
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
309
+ *
310
+ * Use this instead of writing the query by hand, so the definition lives in one place.
311
+ */
244
312
  .FormFieldSelect-module_xapp_checkbox_select__QccWu {
245
313
  margin: 6px !important;
246
314
  font-size: var(--xapp-form-widget-checkbox-font-size, 14px) !important;
@@ -249,6 +317,11 @@
249
317
  padding: 8px 16px !important;
250
318
  height: 32px !important;
251
319
  }
320
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
321
+ .FormFieldSelect-module_xapp_checkbox_select__QccWu {
322
+ height: 44px !important;
323
+ }
324
+ }
252
325
 
253
326
  .FormFieldSelect-module_xapp_select_container__HWy4J {
254
327
  display: flex;
@@ -269,6 +342,23 @@
269
342
  .FormFieldCard-module_xapp_form_card__AcVAf img {
270
343
  width: 50% !important;
271
344
  }
345
+ /**
346
+ * The phone breakpoint.
347
+ *
348
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
349
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
350
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
351
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
352
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
353
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
354
+ *
355
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
356
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
357
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
358
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
359
+ *
360
+ * Use this instead of writing the query by hand, so the definition lives in one place.
361
+ */
272
362
  .MuiChip-label {
273
363
  padding-left: 4px !important;
274
364
  padding-right: 4px !important;
@@ -304,10 +394,11 @@
304
394
  outline: 2px solid var(--xapp-form-widget-focus-ring-color, var(--xapp-form-widget-header-background-color, #012b54));
305
395
  outline-offset: 0px;
306
396
  }
307
- @media (max-width: 640px) {
397
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
308
398
  .FormFieldChips-module_xapp_checkbox_chip__8DRkb {
309
399
  min-width: 100px !important;
310
400
  font-size: 16px !important;
401
+ height: 44px !important;
311
402
  }
312
403
  .FormFieldChips-module_xapp_checkbox_chip__8DRkb .MuiChip-label {
313
404
  margin: 0;
@@ -332,7 +423,7 @@
332
423
  margin: 0 2px;
333
424
  text-align: center;
334
425
  }
335
- @media (max-width: 640px) {
426
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
336
427
  .FormFieldChips-module_xapp_chip_wrapper__AGfKl {
337
428
  margin: 0 2px;
338
429
  }
@@ -413,6 +504,23 @@
413
504
  .FormFieldTextInput-module_xapp_text_input_text__3rHVn .MuiInputBase-multiline {
414
505
  padding: 0px;
415
506
  }
507
+ /**
508
+ * The phone breakpoint.
509
+ *
510
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
511
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
512
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
513
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
514
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
515
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
516
+ *
517
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
518
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
519
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
520
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
521
+ *
522
+ * Use this instead of writing the query by hand, so the definition lives in one place.
523
+ */
416
524
  .FormFieldDropdown-module_xapp_dropdown_container__4oRlr {
417
525
  margin-top: 20px;
418
526
  margin-bottom: 20px;
@@ -422,12 +530,29 @@
422
530
  font-size: var(--xapp-form-widget-dropdown-font-size, 14px);
423
531
  font-family: var(--xapp-form-widget-dropdown-font-family, var(--xapp-form-widget-font-family, RobotoRegular, serif));
424
532
  }
425
- @media (max-width: 640px) {
533
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
426
534
  .FormFieldDropdown-module_xapp_dropdown_container__4oRlr .MuiInputBase-input,
427
535
  .FormFieldDropdown-module_xapp_dropdown_container__4oRlr select {
428
536
  font-size: var(--xapp-form-widget-dropdown-font-size-mobile, 16px);
429
537
  }
430
538
  }
539
+ /**
540
+ * The phone breakpoint.
541
+ *
542
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
543
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
544
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
545
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
546
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
547
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
548
+ *
549
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
550
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
551
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
552
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
553
+ *
554
+ * Use this instead of writing the query by hand, so the definition lives in one place.
555
+ */
431
556
  .FormFieldDate-module_xapp_date_picker_container__d8LYB {
432
557
  height: 100%;
433
558
  display: flex;
@@ -531,7 +656,7 @@
531
656
  * only fits once the 2px side margins on each cell go - hence dropping the gap rather than
532
657
  * the cell, per the issue.
533
658
  */
534
- @media (max-width: 640px) {
659
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
535
660
  .FormFieldDate-module_xapp_date_picker__Rvtj1 .MuiPickersDay-root,
536
661
  .FormFieldDate-module_xapp_date_picker__Rvtj1 .MuiPickersDay-dayWithMargin {
537
662
  width: 44px !important;
@@ -552,6 +677,167 @@
552
677
  height: 44px !important;
553
678
  }
554
679
  }
680
+ /**
681
+ * The phone breakpoint.
682
+ *
683
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
684
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
685
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
686
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
687
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
688
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
689
+ *
690
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
691
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
692
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
693
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
694
+ *
695
+ * Use this instead of writing the query by hand, so the definition lives in one place.
696
+ */
697
+ .FormFieldDateTime-module_xapp_datetime__rPNwE {
698
+ display: flex;
699
+ flex-direction: column;
700
+ align-items: center;
701
+ width: 100%;
702
+ font-family: var(--xapp-form-widget-date-font-family, var(--xapp-form-widget-font-family, RobotoRegular, serif));
703
+ }
704
+
705
+ .FormFieldDateTime-module_xapp_datetime_title__VNHwW {
706
+ margin: 0 0 8px;
707
+ font-family: inherit;
708
+ font-size: 1rem;
709
+ text-align: center;
710
+ }
711
+
712
+ /* Calendar and column side by side on a wide enough viewport.
713
+ *
714
+ * `flex-wrap` rather than a fixed two-column grid: the pair has to be allowed to fall
715
+ * onto two rows rather than force the step to scroll sideways, which is the failure the
716
+ * mobile rule below would otherwise only fix at the breakpoint. */
717
+ .FormFieldDateTime-module_xapp_datetime_body__ta9Ui {
718
+ display: flex;
719
+ flex-wrap: wrap;
720
+ justify-content: center;
721
+ align-items: flex-start;
722
+ gap: 16px;
723
+ width: 100%;
724
+ }
725
+
726
+ .FormFieldDateTime-module_xapp_datetime_calendar__Ge5W6 {
727
+ flex: 0 0 auto;
728
+ }
729
+
730
+ /* The zone notice and the column travel together, so the sizing the column used to own
731
+ * lives here now - the column itself keeps only the scrolling, which the notice must
732
+ * stay outside of or it scrolls away from the times it describes. */
733
+ .FormFieldDateTime-module_xapp_datetime_times_column__UY7ho {
734
+ flex: 1 1 160px;
735
+ display: flex;
736
+ flex-direction: column;
737
+ gap: 8px;
738
+ min-width: 0;
739
+ max-width: 240px;
740
+ }
741
+
742
+ .FormFieldDateTime-module_xapp_datetime_timezone__ZE56Q {
743
+ margin: 0;
744
+ padding: 0 4px;
745
+ font-size: var(--xapp-form-widget-date-font-size, 14px);
746
+ text-align: left;
747
+ }
748
+
749
+ /* A column of buttons rather than chips: a half-hour schedule produces 16 or more
750
+ * offerings and chips wrap into an unreadable block past a handful. */
751
+ .FormFieldDateTime-module_xapp_datetime_times__rhU-O {
752
+ display: flex;
753
+ flex-direction: column;
754
+ gap: 8px;
755
+ min-width: 0;
756
+ max-height: 320px;
757
+ overflow-y: auto;
758
+ padding: 4px;
759
+ }
760
+
761
+ .FormFieldDateTime-module_xapp_datetime_group__CeL-E {
762
+ position: sticky;
763
+ top: 0;
764
+ z-index: 1;
765
+ margin: 4px 0 0;
766
+ padding: 4px 0;
767
+ background-color: #ffffff;
768
+ font-family: inherit;
769
+ font-size: var(--xapp-form-widget-date-font-size, 14px);
770
+ font-weight: 600;
771
+ text-align: left;
772
+ }
773
+
774
+ .FormFieldDateTime-module_xapp_datetime_time__x5lxl {
775
+ flex: 0 0 auto;
776
+ min-height: 44px;
777
+ padding: 8px 12px;
778
+ border: 1px solid var(--xapp-form-widget-chips-background-color, #c4dced);
779
+ border-radius: var(--xapp-form-widget-border-radius-sm, 8px);
780
+ background-color: transparent;
781
+ color: var(--xapp-form-widget-chips-color, #000000);
782
+ font-family: var(--xapp-form-widget-chips-font-family, var(--xapp-form-widget-font-family, RobotoRegular, serif));
783
+ font-size: var(--xapp-form-widget-chips-font-size, 0.875em);
784
+ font-weight: 600;
785
+ cursor: pointer;
786
+ transition: background-color 200ms ease-in-out, box-shadow 200ms ease-in-out, transform 150ms ease-in-out;
787
+ }
788
+ .FormFieldDateTime-module_xapp_datetime_time__x5lxl:hover {
789
+ background-color: var(--xapp-form-widget-chips-background-color, #c4dced);
790
+ box-shadow: var(--xapp-form-widget-box-shadow-subtle, 0 2px 8px rgba(0, 0, 0, 0.08));
791
+ }
792
+ .FormFieldDateTime-module_xapp_datetime_time__x5lxl:active {
793
+ transform: scale(0.98);
794
+ }
795
+ .FormFieldDateTime-module_xapp_datetime_time__x5lxl:focus {
796
+ outline: none;
797
+ }
798
+ .FormFieldDateTime-module_xapp_datetime_time__x5lxl:focus-visible {
799
+ outline: 2px solid var(--xapp-form-widget-focus-ring-color, var(--xapp-form-widget-header-background-color, #012b54));
800
+ outline-offset: 0px;
801
+ }
802
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
803
+ .FormFieldDateTime-module_xapp_datetime_time__x5lxl {
804
+ font-size: 16px;
805
+ }
806
+ }
807
+
808
+ .FormFieldDateTime-module_xapp_datetime_time_selected__IRT84 {
809
+ border-color: var(--xapp-form-widget-chips-background-color-selected, var(--xapp-form-widget-chips-background-color-dark, #6e7ae1));
810
+ background-color: var(--xapp-form-widget-chips-background-color-selected, var(--xapp-form-widget-chips-background-color-dark, #6e7ae1));
811
+ color: var(--xapp-form-widget-chips-color-selected, #ffffff);
812
+ }
813
+ .FormFieldDateTime-module_xapp_datetime_time_selected__IRT84:hover {
814
+ background-color: var(--xapp-form-widget-chips-background-color-selected, var(--xapp-form-widget-chips-background-color-dark, #6e7ae1));
815
+ }
816
+
817
+ .FormFieldDateTime-module_xapp_datetime_message__4rf-S {
818
+ margin: 8px 0;
819
+ font-size: var(--xapp-form-widget-date-font-size, 14px);
820
+ text-align: center;
821
+ }
822
+
823
+ .FormFieldDateTime-module_xapp_datetime_error__bTyZK {
824
+ margin-top: 14px;
825
+ }
826
+
827
+ /* Stacked, with the column under the calendar and given room to scroll on its own. */
828
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
829
+ .FormFieldDateTime-module_xapp_datetime_body__ta9Ui {
830
+ flex-direction: column;
831
+ align-items: center;
832
+ }
833
+ .FormFieldDateTime-module_xapp_datetime_times_column__UY7ho {
834
+ width: 100%;
835
+ max-width: 320px;
836
+ }
837
+ .FormFieldDateTime-module_xapp_datetime_times__rhU-O {
838
+ max-height: 260px;
839
+ }
840
+ }
555
841
  .FormFieldTextInputAddress-module_xapp_text_input_address_container__title__IbovL p {
556
842
  margin: 0;
557
843
  font-family: var(--xapp-form-widget-text-font-family, var(--xapp-form-widget-font-family, RobotoRegular, serif));
@@ -606,6 +892,23 @@
606
892
  .MuiAutocomplete-popper {
607
893
  z-index: 16000 !important;
608
894
  }
895
+ /**
896
+ * The phone breakpoint.
897
+ *
898
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
899
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
900
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
901
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
902
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
903
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
904
+ *
905
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
906
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
907
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
908
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
909
+ *
910
+ * Use this instead of writing the query by hand, so the definition lives in one place.
911
+ */
609
912
  .FormStepDisplay-module_xapp_step_iframe_wrapper__BBFRw {
610
913
  display: flex;
611
914
  flex-direction: column;
@@ -619,7 +922,7 @@
619
922
  margin-left: -56px;
620
923
  margin-right: -56px;
621
924
  }
622
- @media (max-width: 640px) {
925
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
623
926
  .FormStepDisplay-module_xapp_step_full_bleed__rhGGK {
624
927
  margin-left: calc(-1 * (8px + env(safe-area-inset-left, 0px)));
625
928
  margin-right: calc(-1 * (8px + env(safe-area-inset-right, 0px)));
@@ -743,6 +1046,7 @@
743
1046
  background-color: var(--xapp-form-widget-primary-button-color, #ea6539) !important;
744
1047
  font-family: inherit !important;
745
1048
  border-radius: var(--xapp-form-widget-border-radius-md, 12px) !important;
1049
+ min-height: 44px !important;
746
1050
  transition: box-shadow 200ms ease-in-out, transform 150ms ease-in-out, opacity 200ms ease-in-out !important;
747
1051
  }
748
1052
  .FormStepDisplay-module_xapp_primary_button__d2wra:hover {
@@ -764,6 +1068,7 @@
764
1068
  background-color: var(--xapp-form-widget-secondary-button-color, #d24cc7) !important;
765
1069
  font-family: inherit !important;
766
1070
  border-radius: var(--xapp-form-widget-border-radius-md, 12px) !important;
1071
+ min-height: 44px !important;
767
1072
  transition: box-shadow 200ms ease-in-out, transform 150ms ease-in-out, opacity 200ms ease-in-out !important;
768
1073
  }
769
1074
  .FormStepDisplay-module_xapp_secondary_button__LuMfN:hover {
@@ -785,6 +1090,7 @@
785
1090
  background-color: rgba(121, 117, 133, 0.5) !important;
786
1091
  font-family: inherit !important;
787
1092
  border-radius: var(--xapp-form-widget-border-radius-md, 12px) !important;
1093
+ min-height: 44px !important;
788
1094
  cursor: not-allowed !important;
789
1095
  }
790
1096
  /**
@@ -972,6 +1278,23 @@
972
1278
  .FormDisplay-module_xapp_header_container_showcase__MWJfr .MuiTypography-root {
973
1279
  color: var(--xapp-form-widget-header-text-color, #b7c5d1) !important;
974
1280
  }
1281
+ /**
1282
+ * The phone breakpoint.
1283
+ *
1284
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
1285
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
1286
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
1287
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
1288
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
1289
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
1290
+ *
1291
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
1292
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
1293
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
1294
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
1295
+ *
1296
+ * Use this instead of writing the query by hand, so the definition lives in one place.
1297
+ */
975
1298
  .SearchResponseOutputSpeech-module_xapp_search_response_output_speech__DCf8F {
976
1299
  font-family: var(--xapp-form-widget-font-family, RobotoRegular, serif);
977
1300
  font-weight: normal;
@@ -985,6 +1308,23 @@
985
1308
  .SearchResponseOutputSpeech-module_xapp_search_response_output_speech__DCf8F p:last-child {
986
1309
  margin-bottom: 0;
987
1310
  }
1311
+ /**
1312
+ * The phone breakpoint.
1313
+ *
1314
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
1315
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
1316
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
1317
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
1318
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
1319
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
1320
+ *
1321
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
1322
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
1323
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
1324
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
1325
+ *
1326
+ * Use this instead of writing the query by hand, so the definition lives in one place.
1327
+ */
988
1328
  .Button-module_xapp_search_btn__cQf3T {
989
1329
  display: inline-block;
990
1330
  border-radius: var(--xapp-form-widget-border-radius-md, 12px);
@@ -1018,6 +1358,23 @@
1018
1358
  .Button-module_xapp_search_btn__expand__dUwot {
1019
1359
  width: 100%;
1020
1360
  }
1361
+ /**
1362
+ * The phone breakpoint.
1363
+ *
1364
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
1365
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
1366
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
1367
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
1368
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
1369
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
1370
+ *
1371
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
1372
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
1373
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
1374
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
1375
+ *
1376
+ * Use this instead of writing the query by hand, so the definition lives in one place.
1377
+ */
1021
1378
  .SuggestedAction-module_xapp_search_suggested_action__gbLCz {
1022
1379
  display: inline-block;
1023
1380
  border-radius: var(--xapp-form-widget-border-radius-md, 12px);
@@ -1067,6 +1424,23 @@
1067
1424
  padding: 0 10px;
1068
1425
  overflow: auto;
1069
1426
  }
1427
+ /**
1428
+ * The phone breakpoint.
1429
+ *
1430
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
1431
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
1432
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
1433
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
1434
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
1435
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
1436
+ *
1437
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
1438
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
1439
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
1440
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
1441
+ *
1442
+ * Use this instead of writing the query by hand, so the definition lives in one place.
1443
+ */
1070
1444
  .FormWidget-module_loading__aAJ-B {
1071
1445
  background-color: rgba(0, 0, 0, 0) !important;
1072
1446
  border: 0px !important;
@@ -1173,9 +1547,10 @@
1173
1547
  }
1174
1548
  }
1175
1549
  /* Mobile */
1176
- @media (max-width: 640px) {
1550
+ @media (max-width: 640px), (max-height: 480px) and (pointer: coarse) {
1177
1551
  .FormWidget-module_xapp_form_widget__V-G-H {
1178
1552
  width: 100%;
1553
+ max-width: none;
1179
1554
  height: 100%;
1180
1555
  border-radius: 0;
1181
1556
  border: 0;
@@ -1188,6 +1563,23 @@
1188
1563
  overflow-y: auto;
1189
1564
  }
1190
1565
  }
1566
+ /**
1567
+ * The phone breakpoint.
1568
+ *
1569
+ * Width alone cannot express "phone". A phone on its side is 740-863px wide - wider than
1570
+ * an iPad in portrait - so `max-width: 640px` silently excluded every landscape phone, and
1571
+ * with it the full-screen panel, the full-bleed modal, the 44px hit boxes, the safe-area
1572
+ * insets and the soft-keyboard padding. Measured on 2026-08-13: in landscape the chat
1573
+ * input sat ~22px from the bottom of a 340px viewport, so any keyboard covered it, and the
1574
+ * form step's action row was unreachable. XappMedia/chat-widget#1561.
1575
+ *
1576
+ * The second arm adds short-and-touch, which is what a landscape phone is. Verified in
1577
+ * Chromium against device descriptors: it matches iPhone 14, Pixel 7 and Galaxy S8 in
1578
+ * landscape, and matches no iPad in either orientation and no desktop. `pointer: coarse`
1579
+ * reports the PRIMARY pointer, so a touch laptop driven by a trackpad stays on desktop.
1580
+ *
1581
+ * Use this instead of writing the query by hand, so the definition lives in one place.
1582
+ */
1191
1583
  .SideButton-module_xapp_form_sticky_button__YqORL {
1192
1584
  position: fixed;
1193
1585
  z-index: 10000;