url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://www.linkedin.com/company/suprsend?trk=organization_guest_main-feed-card_feed-actor-image | SuprSend | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join for free SuprSend Software Development San Francisco, CA 19,129 followers Communication Infrastructure for dev & product teams See jobs Follow View all 17 employees Report this company About us SuprSend is a central communication stack for easily creating, managing and delivering notifications to your end users on multiple channels. Our single notification API has all the features set, which enables you to send notifications in a reliable and scalable manner and take care of end user experience, thereby eliminating the need to develop any notification service in-house for transactional/engagement notifications. Website https://www.suprsend.com/ External link for SuprSend Industry Software Development Company size 11-50 employees Headquarters San Francisco, CA Type Privately Held Founded 2021 Specialties notifications, android push, ios push, email, sms, whatsapp, slack, Microsoft teams, Telegram, App Inbox, A/B Experiments, web push, RCS, preferences management, batching & digests, notification infrastructure, twilio, template builder, inapp inbox, and react sdk Products SuprSend SuprSend Push Notification Software SuprSend is a notification infrastructure as a service platform for easily creating, managing, and delivering notifications to your end users. SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack are that: * You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritize vendors and channels from your SuprSend account, * You can design powerful templates for all channels together and manage them from a single place, * You can leverage powerful features to experiment fast with notifications and take care of end-user experience without writing a single line of code. Locations Primary San Francisco, CA 94104, US Get directions Bengaluru, KA 560102, IN Get directions Employees at SuprSend Deepak Deolalikar Samuel Sunderaraj Gaurav Verma Sathya Nellore Sampat See all employees Updates SuprSend reposted this SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 2w Report this post [𝗟𝗜𝗩𝗘] 𝗛𝗼𝘀𝘁𝗲𝗱 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲: 𝗥𝗲𝗮𝗱𝘆-𝘁𝗼-𝘂𝘀𝗲 𝘂𝘀𝗲𝗿 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 🌍 SuprSend now gives you a ready-made Preference Page where users can manage how they receive notifications. Just link to it from your emails or SMS — no need to build or maintain your own preference system. It’s designed to help you stay compliant while giving users better control over their communication. We’ve now added full localization support so these pages work seamlessly for global audiences. What’s new: • Pages adapt automatically to the user’s locale • Category names, descriptions, and sections are rendered dynamically • Static page text is localized • Smart fallback when a regional language isn’t available If you’re sending notifications across regions, this makes preference management clearer for users and easier to scale for teams. Preview link in the comments. 5 Like Comment Share SuprSend 19,129 followers 3w Edited Report this post 𝗘𝘅𝗽𝗼𝗿𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗗𝗮𝘁𝗮 𝘁𝗼 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝟯 🚀 Now you can fully own and control your notifications data within your S3 bucket — create custom dashboards, debug delivery issues, or maintain audit trails for compliance. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝗰𝗹𝘂𝗱𝗲𝗱: • Syncs every 5 minutes in encrypted Parquet files • Messages, Workflow Executions, and Requests • Automatic backfills and hourly partitions • Works natively with Athena, Snowflake, BigQuery, Redshift Confidently build dashboards, surface notification logs to customers, or track entire customer lifecycle end-to-end. Docs in comments 👇 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new UI / UX Designer in Bengaluru, Karnataka. Apply today or share this post with your network. UI / UX Designer SuprSend, Bengaluru, Karnataka, India 7 Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝘆 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗖𝗲𝗻𝘁𝗲𝗿𝘀 🌍 In pursuit of seamless translations: preference categories now display in your user's locale. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗺𝗲𝗮𝗻𝘀: • One preference center works globally (no separate versions for each region) • Users make informed choices when they see categories in their preferred language • Add translations through Dashboard, API, or CLI • Smart fallback logic ensures something always displays (es-mx → es → en) If you're shipping notifications to a multilingual audience, this removes friction for both your users and your team. Docs in comments below 👇 13 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post 𝗛𝗼𝘄 𝗖𝗿𝗮𝘇𝘆𝗚𝗮𝗺𝗲𝘀 𝗖𝘂𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗳𝗿𝗼𝗺 𝗪𝗲𝗲𝗸𝘀 𝘁𝗼 𝗛𝗼𝘂𝗿𝘀 CrazyGames serves 45M+ monthly players across 3,000+ browser games. But their in-house notification system held them back. 🎮 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: Building notifications required heavy engineering involvement. Even small template changes meant creating dev tickets and took 2 weeks to deploy. Product teams couldn't personalize or experiment fast without developer time. 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱: CrazyGames adopted SuprSend to abstract notification development out of code. Templates, logic, and workflows shifted entirely to Product & Design. They also connected their database to SuprSend, allowing teams to create targeted cohorts by writing SQL — no data exports, no syncing delays, no engineering bottlenecks. 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁: • Notification launches: weeks → hours • Self-serve campaigns with personalized game recommendations • A/B testing across email, push, and in-app — all unified • Product teams operate independently 🎥 Watch Jonas (VP of Product, CrazyGames) full story link in comments below. 33 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Founders’ Office – Product Marketing in Bengaluru, Karnataka. Apply today or share this post with your network. Product Marketing Manager SuprSend, Bengaluru, Karnataka, India 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 Maintaining separate notification templates for every language doesn't scale. Change one template and you update all language versions manually. Translations solve this. Write one template that works across all languages. SuprSend automatically serves the right language based on user locale, with intelligent fallbacks. What's included: • Upload existing JSON translation files & manage through CLI/API • Smart translation keys with automatic language selection • Dynamic variables and pluralization handling • Namespaced keys to organize by feature • Change history with rollback support Documentation in the comments 👇 13 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Product Manager in Bengaluru, Karnataka. Apply today or share this post with your network. Product Manager SuprSend, Bengaluru, Karnataka, India 4 Like Comment Share Join now to see what you are missing Find people you know at SuprSend Browse recommended jobs for you View all updates, news, and articles Join now Similar pages SuperSend Software Development Las Vegas, Nevada Crew Technology, Information and Internet Keploy 🐰 Technology, Information and Internet San Franciso, California KubeSense Software Development Austin, Texas Gushwork Software Development Brooklyn, New York Robylon AI Software Development San Francisco, California Cube Technology, Information and Internet Palo Alto, California Klaar Software Development San Francisco, California Bik.ai Technology, Information and Internet Zime Data Infrastructure and Analytics San Jose, CA Show more similar pages Show fewer similar pages Browse jobs Engineer jobs 555,845 open jobs Product Marketer jobs 9,108 open jobs Marketing Manager jobs 106,879 open jobs Scientist jobs 48,969 open jobs Machine Learning Engineer jobs 148,937 open jobs Developer jobs 258,935 open jobs Marketer jobs 37,677 open jobs Intelligence Specialist jobs 7,156 open jobs Intern jobs 71,196 open jobs Python Developer jobs 46,642 open jobs Senior Product Marketing Manager jobs 11,129 open jobs Analyst jobs 694,057 open jobs Manager jobs 1,880,925 open jobs Associate Product Manager jobs 76,300 open jobs General Engineer jobs 54,597 open jobs Software Engineer jobs 300,699 open jobs Associate jobs 1,091,945 open jobs Account Manager jobs 121,519 open jobs Marketing Specialist jobs 49,178 open jobs Digital Marketing Manager jobs 17,135 open jobs Show more jobs like this Show fewer jobs like this Funding SuprSend 1 total round Last Round Seed Oct 14, 2022 External Crunchbase Link for last round of funding US$ 1.0M Investors BoldCap + 4 Other investors See more info on crunchbase More searches More searches Engineer jobs Developer jobs Marketing Manager jobs Machine Learning Engineer jobs Intelligence Specialist jobs Scientist jobs Associate Product Manager jobs Analyst jobs Software Engineer jobs Intern jobs Product Management Intern jobs Talent Specialist jobs Global Marketing Manager jobs Consultant jobs Marketing Lead jobs Marketing Specialist jobs Product Marketer jobs Writer jobs Frontend Developer jobs Program Management Intern jobs Product Manager jobs Associate Project Manager jobs Network Developer jobs Account Manager jobs Digital Marketing Manager jobs Manager jobs Product Engineer jobs Senior Developer jobs Application Engineer jobs Customer Service Technician jobs Advocate jobs Linux Developer jobs Security Administrator jobs Web Developer jobs Senior Software Engineer jobs Full Stack Engineer jobs Data Scientist jobs Curriculum Developer jobs Sales Trainer jobs Science Specialist jobs Web Development Specialist jobs Security Engineer jobs Software Engineer Intern jobs Staff Software Engineer jobs Technology Engineer jobs Lead Software Engineer jobs Research Software Engineer jobs Business Development Associate jobs Technician jobs Content Specialist jobs iOS Developer jobs Senior Product Manager jobs User Interface Designer jobs PHP Developer jobs Product Designer jobs Director jobs Bookkeeper jobs User Experience Designer jobs Operations Engineer jobs Founder jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at SuprSend Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/feature-importer/ | DevCycle Feature Flag Importer | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page DevCycle Feature Flag Importer DevCycle's Feature Flag Importer is designed to import resources from other Feature Flag providers. The Importer is intended to be run on a single Project and will create or update a Project with the same key containing Environments, Features, and Variables. info The Feature Importer script is fully open-source. Check it out here: https://github.com/devcyclehq/feature-importer Tutorial Video Setup Clone repo from here . Run npm install to install dependencies. Setup configuration file . Run npm start to start an import. Configuration File The Feature Importer can be configured using environment variables or a JSON config file. By default the config is read from config.json in the project root, this can be overwritten using CONFIG_FILE_PATH . info The Feature Importer only supports LaunchDarkly API Version 20220603 . Please select this version when creating an API access token in LaunchDarkly. Required ldAccessToken : string LaunchDarkly access token. Used for pulling Feature Flags. Equivalent env var: LD_ACCESS_TOKEN dvcClientId : string DevCycle client ID. Used for fetching API credentials. Equivalent env var: DVC_CLIENT_ID dvcClientSecret : string DevCycle client secret. Used for fetching API credentials. Equivalent env var: DVC_CLIENT_SECRET sourceProjectKey : string LaunchDarkly's Project key. Resources will be pulled from this Project. Equivalent env var: SOURCE_PROJECT_KEY Optional targetProjectKey : string A DevCycle Project key. Resources will be created within this Project. A Project will be created with this key if it does not already exist. If not specified, the target Project key will be used Equivalent env var: TARGET_PROJECT_KEY includeFeatures : string[] An array of LD Feature Flag keys to be imported. By default, the Importer will attempt to migrate all Features. Equivalent env var: INCLUDE_FEATURES excludeFeatures : string[] An array of LD Feature Flag keys to be skipped when importing. Equivalent env var: EXCLUDE_FEATURES overwriteDuplicates : boolean If true, when the Importer encounters a duplicate resource it will be overwritten. By default, duplicates will be skipped. Equivalent env var: OVERWRITE_DUPLICATES operationMap : Map<string, string> A map of LD operations to map to DevCycle operations DevCycle operations: = , != , > , < , >= , <= , contain , !contain , exist , !exist Equivalent env var: OPERATION_MAP Sample config.json file: { "ldAccessToken" : "api-key" , "dvcClientId" : "clientId" , "dvcClientSecret" : "clientSecret" , "sourceProjectKey" : "project-key" , "includeFeatures" : [ "feat-1" , "feat-2" ] , "excludeFeatures" : [ ] , "overwriteDuplicates" : false , "operationMap" : { "startsWith" : "contain" , "endsWith" : "contain" } } Sample .env file: LD_ACCESS_TOKEN="api-key" DVC_CLIENT_ID="clientId" DVC_CLIENT_SECRET="clientSecret" SOURCE_PROJECT_KEY="project-key" INCLUDE_FEATURES=[feat-1,feat-2] EXCLUDE_FEATURES=[] OVERWRITE_DUPLICATES=false OPERATION_MAP='{"endsWith":"contain","startsWith":"contain"}' Code Migration Migrating Code from LaunchDarkly In LaunchDarkly, the primary identifier is key , in DVC the equivalent value should be passed as user_id DVC supports the following top-level properties on the user object: see DVC User Object . Any other properties used for Targeting should be passed within the customData map. If you are passing a date to be used with LD's before/after operators, the value should be converted to a Long when passed to DVC. The Importer will convert before & after operators to < & > in DVC. DVC doesn't support Targeting by the top-level isAnonymous property. If you are using LD's Targeting with the anonymous attribute, make sure to include an anonymous property in the user's customData Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with Features and more within a DevCycle Project, as well as the DevCycle Bucketing API which is used to give users Features and Variables (as used within the DevCycle SDKs!) Edit this page Last updated on Jan 9, 2026 Tutorial Video Setup Configuration File Code Migration Migrating Code from LaunchDarkly DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.spreaker.com/user/14532324/s2e23-building-a-customer-focused-mindse | S2E23 | Building A Customer-Focused Mindset with Carl Bergenhem Discover Your Library Search For Podcasters Your Podcasts Free Our Platform How Spreaker Works Podcasts App Spreaker Create New Prime Network Help { if (!hidden) { $refs.inputMobile.focus(); } }); if (isSearch && !query) { if (window.innerWidth Sign up Login Sign up For Podcasters Your Podcasts Free Settings Light Theme Dark Theme Our Platform How Spreaker Works Podcasts App Spreaker Create New Prime Network Help { if (this.toast) { this.toast = null; } }, timings[this.toast.type]); }, getClassType() { return { 'bg-neutral-700 dark:bg-neutral-100 text-white dark:text-neutral-950': this .toast?.type === 'default', 'bg-sky-700 text-white': this.toast?.type === 'info', 'bg-emerald-700 text-white': this.toast?.type === 'success', 'bg-red-800 text-white': this.toast?.type === 'error', 'bg-orange-400 text-neutral-950': this.toast?.type === 'warning' } } }" x-on:toast.window="showToast($event.detail)" x-show="toast" class="fixed left-0 right-0 z-10 md:left-[250px]" x-transition> Dev Life S2E23 | Building A Customer-Focused Mindset with Carl Bergenhem Jul 4, 2022 · 58m 49s Loading Play Pause Add to queue In queue { SP.Utils.setDocumentShouldScroll(!opened); })"> Download Download and listen anywhere Download your favorite episodes and enjoy them, wherever you are! Sign up or log in now to access offline listening. Sign up to download { SP.Utils.setDocumentShouldScroll(!opened); })"> Embed Embed episode `; }, copyToClipboard() { this.copyStatus = 'DONE'; SP.Utils.copyToClipboard(this.getIframeCode()); setTimeout(() => { this.copyStatus = 'IDLE'; }, 2000); } }"> Dark Light Copy Done Looking to add a personal touch? Explore all the embedding options available in our developer's guide Share on X Share on Facebook Share on Bluesky Share on Whatsapp Share on Telegram Share on LinkedIn Description SHOW SUMMARY: In this episode of NgXP, we ask how you can build a customer-focused mindset as a software engineer. And who better to help us with this discussion than... show more SHOW SUMMARY: In this episode of NgXP, we ask how you can build a customer-focused mindset as a software engineer. And who better to help us with this discussion than Carl Bergenhem, the Principal Product Manager for KendoUI! Carl has spent his career becoming an expert in helping individuals, teams, and entire organizations go from being ‘feature factories’ to empathetic developers of top-notch, customer-focused products. He gives great advice for how to implement these practices into your teams and shares how you’ll find greater job satisfaction than ever before. LINKS: https://twitter.com/carlbergenhem https://www.telerik.com/kendo-ui CONNECT WITH US: Carl Bergenhem @carlbergenhem Brooke Avery @JediBravery Erik Slack @erik_slack show less Comments Sign in to leave a comment Information Author Dev Life Podcast Organization Dev Life Podcast Website - Tags #angular #applications #bergenhem #code #coding #customer-focused #customer-service #developer #development #kendoui #programmer #programming #progress #ux/ui #websites 🇬🇧 English 🇬🇧 English 🇮🇹 Italiano 🇪🇸 Espanõl 🇬🇧 English 🇬🇧 English 🇮🇹 Italiano 🇪🇸 Espanõl Terms Privacy {e.preventDefault(); showOneTrustPreferenceCenter();}" class="inline-flex items-center gap-2 hover:underline"> Your Privacy Choices Copyright 2026 - Spreaker Inc. an iHeartMedia Company { SP.Utils.setDocumentShouldScroll(!opened); })"> Playing Now Queue Looks like you don't have any active episode Browse Spreaker Catalogue to discover great new content Browse now Current Looks like you don't have any episodes in your queue Browse Spreaker Catalogue to discover great new content Browse now 1" class="mt-6"> Next Up Manage Done svg]:text-white"> Up Up Down Down Remove svg]:text-white"> It's so quiet here... Time to discover new episodes! Discover Your Library Search { SP.Utils.setDocumentShouldScroll(!opened); })"> Unlock Spreaker's full potential Sign up to keep listening, access your Library to pick up episodes right where you left off, and connect with your favorite creators. Experience the ultimate podcast listening on Spreaker! Sign up for free | 2026-01-13T08:48:25 |
https://www.youtube.com/watch?v=GhN7uxPLSpM | How leaders can create great internship programs - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x29045186dbe0de44"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtPcnJtOVVTelpBOCjUjZjLBjIKCgJLUhIEGgAgDA%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRrnK9kdOioPXbjMoXAptIDzHqDiiN0D34j7HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","avatarStackViewModel","dialogViewModel","dialogHeaderViewModel","badgeViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","markerRenderer","chapterRenderer","notificationActionRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","macroMarkersListRenderer","macroMarkersListItemRenderer","toggleButtonRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionCourseSectionRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","topicLinkRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtPcnJtOVVTelpBOCjUjZjLBjIKCgJLUhIEGgAgDA%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwil1PbtkIiSAxWqS3gAHfsnODAyDHJlbGF0ZWQtYXV0b0iTla2esffeiRqaAQUIAxD4HcoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwil1PbtkIiSAxWqS3gAHfsnODAyDHJlbGF0ZWQtYXV0b0iTla2esffeiRqaAQUIAxD4HcoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwil1PbtkIiSAxWqS3gAHfsnODAyDHJlbGF0ZWQtYXV0b0iTla2esffeiRqaAQUIAxD4HcoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"How leaders can create great internship programs"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 267회"},"shortViewCount":{"simpleText":"조회수 267회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CMkCELW0CRgAIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC0doTjd1eFBMU3BNGmBFZ3RIYUU0M2RYaFFURk53VFVBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDBkb1RqZDFlRkJNVTNCTkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CMkCELW0CRgAIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}}],"trackingParams":"CMkCELW0CRgAIhMIpdT27ZCIkgMVqkt4AB37Jzgw","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"0","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNQCEKVBIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},{"innertubeCommand":{"clickTrackingParams":"CNQCEKVBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNUCEPqGBCITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNUCEPqGBCITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"GhN7uxPLSpM"},"likeParams":"Cg0KC0doTjd1eFBMU3BNIAAyDAjVjZjLBhCQyID0AQ%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CNUCEPqGBCITCKXU9u2QiJIDFapLeAAd-yc4MA=="}}}}}}}]}},"accessibilityText":"이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNQCEKVBIhMIpdT27ZCIkgMVqkt4AB37Jzgw","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"1","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNMCEKVBIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},{"innertubeCommand":{"clickTrackingParams":"CNMCEKVBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"GhN7uxPLSpM"},"removeLikeParams":"Cg0KC0doTjd1eFBMU3BNGAAqDAjVjZjLBhDas4H0AQ%3D%3D"}}}]}},"accessibilityText":"이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNMCEKVBIhMIpdT27ZCIkgMVqkt4AB37Jzgw","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CMkCELW0CRgAIhMIpdT27ZCIkgMVqkt4AB37Jzgw","isTogglingDisabled":true}},"likeStatusEntityKey":"EgtHaE43dXhQTFNwTSA-KAE%3D","likeStatusEntity":{"key":"EgtHaE43dXhQTFNwTSA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNECEKiPCSITCKXU9u2QiJIDFapLeAAd-yc4MA=="}},{"innertubeCommand":{"clickTrackingParams":"CNECEKiPCSITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNICEPmGBCITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNICEPmGBCITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"GhN7uxPLSpM"},"dislikeParams":"Cg0KC0doTjd1eFBMU3BNEAAiDAjVjZjLBhD42IL0AQ%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CNICEPmGBCITCKXU9u2QiJIDFapLeAAd-yc4MA=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNECEKiPCSITCKXU9u2QiJIDFapLeAAd-yc4MA==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNACEKiPCSITCKXU9u2QiJIDFapLeAAd-yc4MA=="}},{"innertubeCommand":{"clickTrackingParams":"CNACEKiPCSITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"GhN7uxPLSpM"},"removeLikeParams":"Cg0KC0doTjd1eFBMU3BNGAAqDAjVjZjLBhCGiIP0AQ%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNACEKiPCSITCKXU9u2QiJIDFapLeAAd-yc4MA==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CMkCELW0CRgAIhMIpdT27ZCIkgMVqkt4AB37Jzgw","isTogglingDisabled":true}},"dislikeEntityKey":"EgtHaE43dXhQTFNwTSA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgtHaE43dXhQTFNwTSD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CM4CEOWWARgDIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},{"innertubeCommand":{"clickTrackingParams":"CM4CEOWWARgDIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtHaE43dXhQTFNwTaABAQ%3D%3D","commands":[{"clickTrackingParams":"CM4CEOWWARgDIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CM8CEI5iIhMIpdT27ZCIkgMVqkt4AB37Jzgw","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CM4CEOWWARgDIhMIpdT27ZCIkgMVqkt4AB37Jzgw","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CMwCEOuQCSITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CM0CEPuGBCITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DGhN7uxPLSpM\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CM0CEPuGBCITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CM0CEPuGBCITCKXU9u2QiJIDFapLeAAd-yc4MA=="}}}}}},"trackingParams":"CMwCEOuQCSITCKXU9u2QiJIDFapLeAAd-yc4MA=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMoCEOuQCSITCKXU9u2QiJIDFapLeAAd-yc4MA=="}},{"innertubeCommand":{"clickTrackingParams":"CMoCEOuQCSITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMsCEPuGBCITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DGhN7uxPLSpM\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMsCEPuGBCITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CMsCEPuGBCITCKXU9u2QiJIDFapLeAAd-yc4MA=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMoCEOuQCSITCKXU9u2QiJIDFapLeAAd-yc4MA==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CMkCELW0CRgAIhMIpdT27ZCIkgMVqkt4AB37Jzgw","superTitleLink":{"runs":[{"text":"The Agile in Action Podcast with Bill Raymond","navigationEndpoint":{"clickTrackingParams":"CMkCELW0CRgAIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLWzwUIYZpnJsGnFUCmugOjrxYFOFNF93B","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLWzwUIYZpnJsGnFUCmugOjrxYFOFNF93B"}}}]},"dateText":{"simpleText":"2024. 1. 8."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"2년 전"}},"simpleText":"2년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Bill Raymond","navigationEndpoint":{"clickTrackingParams":"CMgCEOE5IhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/@bill-raymond","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCo63gWfWRfEciJ98mJLIU0Q","canonicalBaseUrl":"/@bill-raymond"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CMgCEOE5IhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/@bill-raymond","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCo63gWfWRfEciJ98mJLIU0Q","canonicalBaseUrl":"/@bill-raymond"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 7.01천명"}},"simpleText":"구독자 7.01천명"},"trackingParams":"CMgCEOE5IhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCo63gWfWRfEciJ98mJLIU0Q","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CLkCEJsrIhMIpdT27ZCIkgMVqkt4AB37JzgwKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Bill Raymond을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Bill Raymond을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CMcCEPBbIhMIpdT27ZCIkgMVqkt4AB37Jzgw","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CMYCEPBbIhMIpdT27ZCIkgMVqkt4AB37Jzgw","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CL8CEJf5ASITCKXU9u2QiJIDFapLeAAd-yc4MA==","command":{"clickTrackingParams":"CL8CEJf5ASITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CL8CEJf5ASITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CMUCEOy1BBgDIhMIpdT27ZCIkgMVqkt4AB37JzgwMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQRGDvdH","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ282M2dXZldSZkVjaUo5OG1KTElVMFESAggBGAAgBFITCgIIAxILR2hON3V4UExTcE0YAA%3D%3D"}},"trackingParams":"CMUCEOy1BBgDIhMIpdT27ZCIkgMVqkt4AB37Jzgw","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CMQCEO21BBgEIhMIpdT27ZCIkgMVqkt4AB37JzgwMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQRGDvdH","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ282M2dXZldSZkVjaUo5OG1KTElVMFESAggDGAAgBFITCgIIAxILR2hON3V4UExTcE0YAA%3D%3D"}},"trackingParams":"CMQCEO21BBgEIhMIpdT27ZCIkgMVqkt4AB37Jzgw","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CMACENuLChgFIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMACENuLChgFIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CMECEMY4IhMIpdT27ZCIkgMVqkt4AB37Jzgw","dialogMessages":[{"runs":[{"text":"Bill Raymond"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CMMCEPBbIhMIpdT27ZCIkgMVqkt4AB37JzgwMgV3YXRjaMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"CgIIAxILR2hON3V4UExTcE0YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CMMCEPBbIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CMICEPBbIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CMACENuLChgFIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CLkCEJsrIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CL4CEP2GBCITCKXU9u2QiJIDFapLeAAd-yc4MDIJc3Vic2NyaWJlygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DGhN7uxPLSpM%26continue_action%3DQUFFLUhqa1BEcFRrN0w4cGpIbEs0S1dlWGVwNUJGQ0Z0Z3xBQ3Jtc0ttYS1DZER0LW5VVmxYLXkyQmNKWFAyTkxaR0daTjIwOXJ5RDNwQW9HWFE2dWlKYzhyVVpDUHhWdlJoV3FEOHY0TXJLdHh6dnU2elVuNVVKWFh6dWRMZW5Ua2RsVF9pZkppNlJRa1NNMU1LYlVUcm85QjJBNFU0eXR5TV9ZS1cwOEpyZnlkM0Voenh5UnFDbkFuM3VNc0ttM1ZRQUJCdGp0TW9DaWFORkx4eGZWZm9QWjdCTmlRaHpIdmxIcEQ3Qm9CSVZQUlU\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CL4CEP2GBCITCKXU9u2QiJIDFapLeAAd-yc4MMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqa1BEcFRrN0w4cGpIbEs0S1dlWGVwNUJGQ0Z0Z3xBQ3Jtc0ttYS1DZER0LW5VVmxYLXkyQmNKWFAyTkxaR0daTjIwOXJ5RDNwQW9HWFE2dWlKYzhyVVpDUHhWdlJoV3FEOHY0TXJLdHh6dnU2elVuNVVKWFh6dWRMZW5Ua2RsVF9pZkppNlJRa1NNMU1LYlVUcm85QjJBNFU0eXR5TV9ZS1cwOEpyZnlkM0Voenh5UnFDbkFuM3VNc0ttM1ZRQUJCdGp0TW9DaWFORkx4eGZWZm9QWjdCTmlRaHpIdmxIcEQ3Qm9CSVZQUlU","idamTag":"66429"}},"trackingParams":"CL4CEP2GBCITCKXU9u2QiJIDFapLeAAd-yc4MA=="}}}}}},"subscribedEntityKey":"EhhVQ282M2dXZldSZkVjaUo5OG1KTElVMFEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CLkCEJsrIhMIpdT27ZCIkgMVqkt4AB37JzgwKPgdMgV3YXRjaMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"EgIIAxgAIgtHaE43dXhQTFNwTQ%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CLkCEJsrIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CLkCEJsrIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CLsCEMY4IhMIpdT27ZCIkgMVqkt4AB37Jzgw","dialogMessages":[{"runs":[{"text":"Bill Raymond"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CL0CEPBbIhMIpdT27ZCIkgMVqkt4AB37JzgwKPgdMgV3YXRjaMoBBEYO90c=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"CgIIAxILR2hON3V4UExTcE0YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CL0CEPBbIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CLwCEPBbIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}],"timedAnimationData":{"animationTiming":[2009880],"macroMarkersIndex":[0],"animationDurationSecs":1.5,"borderStrokeThicknessDp":2,"borderOpacity":1,"fillOpacity":0,"trackingParams":"CLoCEPBbIhMIpdT27ZCIkgMVqkt4AB37Jzgw","animationOrigin":"ANIMATION_ORIGIN_SMARTIMATION"}}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37Jzgw","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"🌱 Cultivate success by leading with dignity with your internship programs.\n\nRobert Khoury, CEO of Agile Rainmakers, discusses his new book, \"Internship Management: Principles for Designing an Exceptional Internship.\"\n\nIn this podcast, you will learn the following:\n✅ The nine essential principles of management in creating a great internship program\n✅ How to foster a positive, enriching environment for continuous learning and growth\n✅ The importance of 'dignity' in internships for a respectful and growth-centric experience.\n🎉 Some real-world examples of great internship programs\n\nChapters\n\n00:00 Introduction and Guest Presentation\n02:00 Understanding Internship Programs\n09:40 The Importance of Respect in Internships\n18:34 The Role of Buoyancy in Internships\n21:29 Reflecting on Past Internship Experiences\n24:12 Empowering Interns for Success\n30:06 Planning for Successful Internship Programs\n32:22 Conclusion and Contact Information","commandRuns":[{"startIndex":597,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","continuePlayback":true,"startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"0초"}}},{"startIndex":639,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM\u0026t=120s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","continuePlayback":true,"startTimeSeconds":120,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026osts=120\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"2분"}}},{"startIndex":679,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM\u0026t=580s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","continuePlayback":true,"startTimeSeconds":580,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026osts=580\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"9분 40초"}}},{"startIndex":726,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM\u0026t=1114s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","continuePlayback":true,"startTimeSeconds":1114,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026osts=1114\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"18분 34초"}}},{"startIndex":768,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM\u0026t=1289s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","continuePlayback":true,"startTimeSeconds":1289,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026osts=1289\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"21분 29초"}}},{"startIndex":816,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM\u0026t=1452s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","continuePlayback":true,"startTimeSeconds":1452,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026osts=1452\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"24분 12초"}}},{"startIndex":853,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM\u0026t=1806s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","continuePlayback":true,"startTimeSeconds":1806,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026osts=1806\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"30분 6초"}}},{"startIndex":903,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=GhN7uxPLSpM\u0026t=1942s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"GhN7uxPLSpM","continuePlayback":true,"startTimeSeconds":1942,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1a137bbb13cb4a93\u0026ip=1.208.108.242\u0026osts=1942\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"32분 22초"}}}],"styleRuns":[{"startIndex":0,"length":597,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":597,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":602,"length":37,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":639,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":644,"length":35,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":679,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":684,"length":42,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":726,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":731,"length":37,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":768,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":773,"length":43,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":816,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":821,"length":32,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":853,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":858,"length":45,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":903,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":908,"length":35,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":597,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":597,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":602,"length":37,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":639,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":644,"length":35,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":679,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":684,"length":42,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":726,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":731,"length":37,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":768,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":773,"length":43,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":816,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":821,"length":32,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":853,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":858,"length":45,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":903,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":908,"length":35,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CLcCELsvGAMiEwil1PbtkIiSAxWqS3gAHfsnODDKAQRGDvdH","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/next"}},"continuationCommand":{"token":"Eg0SC0doTjd1eFBMU3BNGAYyJSIRIgtHaE43dXhQTFNwTTAAeAJCEGNvbW1lbnRzLXNlY3Rpb24%3D","request":"CONTINUATION_REQUEST_TYPE_WATCH_NEXT"}}}}],"trackingParams":"CLcCELsvGAMiEwil1PbtkIiSAxWqS3gAHfsnODA=","sectionIdentifier":"comment-item-section","targetId":"comments-section"}}],"trackingParams":"CLYCELovIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/yVetSg_l-QI/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLAS5av-zV0e4EW9AZaRHoB083LKjQ","width":168,"height":94},{"url":"https://i.ytimg.com/vi/yVetSg_l-QI/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLB4FwS1cnEYZ_M8U0p8kAm9S5Yzpw","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"30:22","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"yVetSg_l-QI","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"30분 22초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CLUCEPBbIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"yVetSg_l-QI","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CLUCEPBbIhMIpdT27ZCIkgMVqkt4AB37Jzgw","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CLQCEPBbIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"yVetSg_l-QI"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CLQCEPBbIhMIpdT27ZCIkgMVqkt4AB37Jzgw","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CK0CENTEDBgAIhMIpdT27ZCIkgMVqkt4AB37Jzgw"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CLMCEPBbIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CLMCEPBbIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"yVetSg_l-QI","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CLMCEPBbIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["yVetSg_l-QI"],"params":"CAQ%3D"}},"videoIds":["yVetSg_l-QI"],"videoCommand":{"clickTrackingParams":"CLMCEPBbIhMIpdT27ZCIkgMVqkt4AB37JzgwygEERg73Rw==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nf | 2026-01-13T08:48:24 |
https://docs.suprsend.com/docs/react-native-androidpush-integration | Android Push (FCM) - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK SuprSend Client SDK Authentication Javascript Android iOS React Native Android Integration iOS Integration Manage Users Sync Events iOS Push Setup Android Push (FCM) Flutter React Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation React Native Android Push (FCM) Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog React Native Android Push (FCM) OpenAI Open in ChatGPT Step-by-Step guide to setup FCM Push notifications in react native Android app. OpenAI Open in ChatGPT Integration steps 1 Create a Firebase project in the firebase console To start sending notifications from FCM, you’ll have to first create a firebase project. Create a firebase project and application in firebase console with your applications package name which you can find in MainApplication.java or AndroidManifest.xml . 2 Adding google-services.json to your project You can get your Service Account JSON from Firebase Console Project Settings. Download google-services.json and add the file inside your android > app folder. 3 Adding Firebase dependencies and plugins Add the below dependency inside projects build.gradle inside dependencies build.gradle Copy Ask AI dependencies { .. . classpath 'com.google.gms:google-services:4.3.10' // or latest version } Add the below plugin inside the app build.gradle build.gradle Copy Ask AI apply plugin : 'com.google.gms.google-services' Add the below dependency inside apps build.gradle inside dependencies build.gradle Copy Ask AI implementation( "com.google.firebase:firebase-messaging:22.0.0" ) // or latest version 4 Implementing push Push feature can be implemented in two ways: Token Generation and Notification handled By SDK [Recommended] You may use this option if all of your android push notifications are to be handled via SuprSend SDK. We recommend you use this method as it is just a single-step process to just register the service in your application manifest and everything else will be ready. AndroidManifest.xml Copy Ask AI <!--If you are targeting to API 33 (Android 13) you will additional need to add POST_NOTIFICATIONS --> < uses-permission android:name = "android.permission.POST_NOTIFICATIONS" /> < service android:name = "app.suprsend.fcm.SSFirebaseMessagingService" android:enabled = "true" android:exported = "false" > < intent-filter > < action android:name = "com.google.firebase.MESSAGING_EVENT" /> </ intent-filter > </ service > Token Generation and Notification handled By Your Application Once you get a token from Firebase you can pass the token by using the below code javascript Copy Ask AI suprsend . user . setAndroidFcmPush ( fcm_token ); When you get a push notification you will get a payload and it can be passed to the method provided by Suprsend React Native SDK and the notification displaying part will be handled by SDK. javascript Copy Ask AI suprsend . showNotification ( notification_payload ); If notification payload contains key supr_send_n_pl then simply consider this as payload sent from suprsend and pass the payload to suprsend SDK by: if (payload?.data?.supr_send_n_pl) { suprsend.showNotification(payload.data.supr_send_n_pl); } Targeting Android 13 (API-33): In Android13 (API 33) or higher notification permission will be disabled by default so permission needs to be asked to enable notifications if you are targeting android 13 users. You can follow this doc to update to support Andriod 13(API 33), if not already supported: https://developer.android.com/about/versions/13/setup-sdk . Please test the application as well as upgrading to API 33 may causes breaking changes. 1 Add POST_NOTIFICATIONS permission in AndroidManifest.xml if not present already. AndroidManifest.xml Copy Ask AI < manifest ... > < uses-permission android:name = "android.permission.POST_NOTIFICATIONS" /> < application ... > ... </ application > </ manifest > 2 Call the SDK method to show a notification permission popup This method is asynchronous and returns permission values like granted, denied, and never_ask_again. NOTE: This method is asynchronous and returns permission values like granted, denied, and never_ask_again. App.js Copy Ask AI const permission = await Suprsend . askNotificationPermission (); Once permission is granted users can be able to get push notifications. Was this page helpful? Yes No Suggest edits Raise issue Previous Android Integration This document will cover integration steps for Android side of your Flutter application. Next ⌘ I x github linkedin youtube Powered by On this page Integration steps Targeting Android 13 (API-33): | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/URI | URIs | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web URIs Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 한국어 Русский 中文 (简体) URIs Uniform Resource Identifiers (URI) are used to identify "resources" on the web. URIs are commonly used as targets of HTTP requests, in which case the URI represents a location for a resource, such as a document, a photo, binary data. The most common type of URI is a Uniform Resource Locator ( URL ), which is known as the web address . URIs can be used to trigger behaviors other than fetching a resource, including opening an email client, sending text messages, or executing JavaScript, when used in other places such as the href of an HTML <a> link. In this article Reference Guides Specifications See also Reference The URI reference provides details about the components that make up a URI. Schemes The first part of the URI, before the : character, which indicates the protocol the browser must use to fetch the resource. Authority The section that comes after the scheme and before the path. It may have up to three parts: user information, host , and port . Path The section after the authority. Contains data, usually organized in hierarchical form, to identify a resource within the scope of the URI's scheme and authority. Query The section after the path. Contains non-hierarchical data to identify a resource within the scope of the URI's scheme and naming authority along with data in the path component. Fragment An optional part at the end of a URI starting with a # character. It is used to identify a specific part of the resource, such as a section of a document or a position in a video. Guides The URI guides help you work with URIs on the web. Choosing between www and non-www URLs Guidance on when sites should use a www. prefix in URLs ( www.example.com vs example.com ). Specifications Specification Unknown specification See also What is a URL? Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 19, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar URIs Guides Using 'www' in URLs Reference Scheme blob: data: javascript: resource: urn: Authority Path Query Fragment Media fragments Text fragments Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://opencollective.com/socketio | socket.io - Open Collective Solutions Product Organization Search Search Search socket.io COLLECTIVE Open source realtime websocket + 2 more browser node.js Fiscal Host : Open Source Collective We are on a mission to enable real-time bidirectional communication on every platform. This is socket.io's page socket.io Contribute All ways to contribute Budget Transactions Expenses Connect Updates About Submit Expense Contact Actions Submit expense Contact Contribute Become a financial contributor. Financial Contributions Recurring contribution Backers Support us with a monthly donation and help us continue our activities. Starts at $2 USD / month Become a backer Latest activity by + 122 Recurring contribution Sponsors Become a sponsor and get your logo on our website https://socket.io/ with a link to your site. Starts at $100 USD / month Become a sponsor Latest activity by + 788 Custom contribution Donation Make a custom one-time or recurring contribution. Contribute Latest activity by + 1031 Top financial contributors Organizations 1 Streamlabs $ 7,500 USD since Jun 2022 2 Casino Professor $ 7,400 USD since Nov 2019 3 CrediMaxx® GmbH $ 7,100 USD since Mar 2020 4 Bestecasinobonussen.nl $ 7,100 USD since Mar 2020 5 Icons8 $ 7,000 USD since Feb 2018 6 Kasinohai.com $ 7,000 USD since Apr 2020 7 Turtlebet - Nettikasinot $ 6,600 USD since Apr 2020 8 Goread.io $ 6,200 USD since Nov 2020 9 Fortune games $ 6,100 USD since Sep 2019 10 Bitcasino $ 6,000 USD since Sep 2019 Individuals 1 Admin MiniTool $ 6,300 USD since Jan 2020 2 Casinority Australia $ 6,100 USD since Dec 2020 3 www.onlinecasinosdeutschland.de $ 5,100 USD since Dec 2021 4 Parimatch India $ 4,800 USD since Feb 2022 5 automatenspiele.org $ 4,700 USD since Feb 2022 6 Veselin Lalev $ 4,500 USD since Apr 2020 7 Poprey - Buy Instagram Likes $ 4,500 USD since Apr 2022 8 Yiannakis Ttafounas Ttafounas $ 4,000 USD since Sep 2019 9 nongamstopcasinos.net $ 3,900 USD since Sep 2022 10 Erik King $ 3,800 USD since Aug 2021 socket.io is all of us Our contributors 1036 Thank you for supporting socket.io. All contributors Team Financial contributors Damien Arrach... Admin $160 USD Guillermo Rauch Admin Streamlabs $7,500 USD Casino Professor Sponsors $7,400 USD Be like Casino Professor and contribute to sock... CrediMaxx® GmbH Sponsors $7,100 USD Bestecasinobo... Sponsors $7,100 USD Icons8 Sponsors $7,000 USD We appreciate everything you've done for us. It... Kasinohai.com Sponsors $7,000 USD Turtlebet - N... Sponsors $6,600 USD Parhaat nettikasinot Admin MiniTool Sponsors $6,300 USD Goread.io Sponsors $6,200 USD Fortune games Sponsors $6,100 USD Budget Transparent and open finances. All Expenses Transactions Monthly financial contribution to socket.io (Sponsors) Credit from bestecasinozondercruks to socket.io • January 12, 2026 + $100.00 USD Completed Contribution #918075 View Details Monthly financial contribution to socket.io (Sponsors) Credit from Buitenlandse Online Casino to socket.io • January 11, 2026 + $100.00 USD Completed Contribution #917850 View Details Monthly financial contribution to socket.io (Sponsors) Credit from payid casino to socket.io • January 11, 2026 + $100.00 USD Completed Contribution #805758 View Details $ Today’s balance $32,309.58 USD Total raised $883,655.23 USD Total disbursed $851,345.65 USD Estimated annual budget $222,737.00 USD Connect Let’s get the ball rolling! News from socket.io Updates on our activities and progress. Monthly update #5 Please find the 5th issue of our Monthly updates here: https://socket.io/blog/monthly-update-5/ Read more Published on July 8, 2021 by Damien Arrachequesne Monthly update #4 Please find the #4 issue of our Monthly updates here: https://socket.io/blog/monthly-update-4/ Read more Published on May 6, 2021 by Damien Arrachequesne Monthly update #3 Please find the #3 issue of our Monthly updates here: https://socket.io/blog/monthly-update-3/ Read more Published on April 9, 2021 by Damien Arrachequesne View all updates → About Socket.IO aims to make realtime apps possible in every browser and mobile device, blurring the differences between the different transport mechanisms. Our team Damien Arrach... Admin Guillermo Rauch Admin Contact Collective Collaborative, transparent, financial management tool Change language Platform Explainer video How it works Use cases Sign up Log in Join Create a Collective About Fiscal Hosting Discover Find a Fiscal Host Become a sponsor Become a Host Community Open Source Docs & Help Organization About Blog Hiring Terms of service Privacy Policy Security Policy Contact us | 2026-01-13T08:48:25 |
https://www.linkedin.com/legal/privacy-policy?trk=d_checkpoint_rp_requestPasswordReset_ft_privacy_policy | LinkedIn Privacy Policy Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Privacy Policy Effective November 3, 2025 Your Privacy Matters LinkedIn’s mission is to connect the world’s professionals to allow them to be more productive and successful. Central to this mission is our commitment to be transparent about the data we collect about you, how it is used and with whom it is shared. This Privacy Policy applies when you use our Services (described below). We offer our users choices about the data we collect, use and share as described in this Privacy Policy, Cookie Policy , Settings and our Help Center. Key Terms Choices Settings are available to Members of LinkedIn and Visitors are provided separate controls. Learn More . Table of Contents Data We Collect How We Use Your Data How We Share Information Your Choices and Obligations Other Important Information Introduction We are a social network and online platform for professionals. People use our Services to find and be found for business opportunities, to connect with others and find information. Our Privacy Policy applies to any Member or Visitor to our Services. Our registered users (“Members”) share their professional identities, engage with their network, exchange knowledge and professional insights, post and view relevant content, learn and develop skills, and find business and career opportunities. Content and data on some of our Services is viewable to non-Members (“Visitors”). We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. Members and Visitors located in the Designated Countries or the UK can review additional information in our European Regional Privacy Notice . Services This Privacy Policy, including our Cookie Policy applies to your use of our Services. This Privacy Policy applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-branded sites, apps, communications and services offered by LinkedIn (“Services”), including off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins, but excluding services that state that they are offered under a different privacy policy. For California residents, additional disclosures required by California law may be found in our California Privacy Disclosure . Data Controllers and Contracting Parties If you are in the “Designated Countries”, LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you are outside of the Designated Countries, LinkedIn Corporation will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. As a Visitor or Member of our Services, the collection, use and sharing of your personal data is subject to this Privacy Policy and other documents referenced in this Privacy Policy, as well as updates. Change Changes to the Privacy Policy apply to your use of our Services after the “effective date.” LinkedIn (“we” or “us”) can modify this Privacy Policy, and if we make material changes to it, we will provide notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. If you object to any changes, you may close your account. You acknowledge that your continued use of our Services after we publish or send a notice about our changes to this Privacy Policy means that the collection, use and sharing of your personal data is subject to the updated Privacy Policy, as of its effective date. 1. Data We Collect 1.1 Data You Provide To Us You provide data to create an account with us. Registration To create an account you need to provide data including your name, email address and/or mobile number, general location (e.g., city), and a password. If you register for a premium Service, you will need to provide payment (e.g., credit card) and billing information. You create your LinkedIn profile (a complete profile helps you get the most from our Services). Profile You have choices about the information on your profile, such as your education, work experience, skills, photo, city or area , endorsements, and optional verifications of information on your profile (such as verifications of your identity or workplace). You don’t have to provide additional information on your profile; however, profile information helps you to get more from our Services, including helping recruiters and business opportunities find you. It’s your choice whether to include sensitive information on your profile and to make that sensitive information public. Please do not post or add personal data to your profile that you would not want to be publicly available. You may give other data to us, such as by syncing your calendar. Posting and Uploading We collect personal data from you when you provide, post or upload it to our Services, such as when you fill out a form, (e.g., with demographic data or salary), respond to a survey, or submit a resume or fill out a job application on our Services. If you sync your calendars with our Services, we will collect your calendar meeting information to keep growing your network by suggesting connections for you and others, and by providing information about events, e.g. times, places, attendees and contacts. You don’t have to post or upload personal data; though if you don’t, it may limit your ability to grow and engage with your network over our Services. 1.2 Data From Others Others may post or write about you. Content and News You and others may post content that includes information about you (as part of articles, posts, comments, videos) on our Services. We also may collect public information about you, such as professional-related news and accomplishments, and make it available as part of our Services, including, as permitted by your settings, in notifications to others of mentions in the news . Others may sync their calendar with our Services Contact and Calendar Information We receive personal data (including contact information) about you when others import or sync their calendar with our Services, associate their contacts with Member profiles, scan and upload business cards, or send messages using our Services (including invites or connection requests). If you or others opt-in to sync email accounts with our Services, we will also collect “email header” information that we can associate with Member profiles. Customers and partners may provide data to us. Partners We receive personal data (e.g., your job title and work email address) about you when you use the services of our customers and partners, such as employers or prospective employers and applicant tracking systems providing us job application data. Related Companies and Other Services We receive data about you when you use some of the other services provided by us or our Affiliates , including Microsoft. For example, you may choose to send us information about your contacts in Microsoft apps and services, such as Outlook, for improved professional networking activities on our Services or we may receive information from Microsoft about your engagement with their sites and services. 1.3 Service Use We log your visits and use of our Services, including mobile apps. We log usage data when you visit or otherwise use our Services, including our sites, app and platform technology, such as when you view or click on content (e.g., learning video) or ads (on or off our sites and apps), perform a search, install or update one of our mobile apps, share articles or apply for jobs. We use log-ins, cookies, device information and internet protocol (“IP”) addresses to identify you and log your use. 1.4 Cookies and Similar Technologies We collect data through cookies and similar technologies. As further described in our Cookie Policy , we use cookies and similar technologies (e.g., pixels and ad tags) to collect data (e.g., device IDs) to recognize you and your device(s) on, off and across different services and devices where you have engaged with our Services. We also allow some others to use cookies as described in our Cookie Policy. If you are outside the Designated Countries, we also collect (or rely on others, including Microsoft, who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. Learn more . You can opt out from our use of data from cookies and similar technologies that track your behavior on the sites of others for ad targeting and other ad-related purposes. For Visitors, the controls are here . 1.5 Your Device and Location We receive data through cookies and similar technologies When you visit or leave our Services (including some plugins and our cookies or similar technology on the sites of others), we receive the URL of both the site you came from and the one you go to and the time of your visit. We also get information about your network and device (e.g., IP address, proxy server, operating system, web browser and add-ons, device identifier and features, cookie IDs and/or ISP, or your mobile carrier). If you use our Services from a mobile device, that device will send us data about your location based on your phone settings. We will ask you to opt-in before we use GPS or other tools to identify your precise location. 1.6 Communications If you communicate through our Services, we learn about that. We collect information about you when you communicate with others through our Services (e.g., when you send, receive, or engage with messages, events, or connection requests, including our marketing communications). This may include information that indicates who you are communicating with and when. We also use automated systems to support and protect our site. For example, we use such systems to suggest possible responses to messages and to manage or block content that violates our User Agreement or Professional Community Policies . 1.7 Workplace and School Provided Information When your organization (e.g., employer or school) buys a premium Service for you to use, they give us data about you. Others buying our Services for your use, such as your employer or your school, provide us with personal data about you and your eligibility to use the Services that they purchase for use by their workers, students or alumni. For example, we will get contact information for “ LinkedIn Page ” (formerly Company Page) administrators and for authorizing users of our premium Services, such as our recruiting, sales or learning products. 1.8 Sites and Services of Others We get data when you visit sites that include our ads, cookies or plugins or when you log-in to others’ services with your LinkedIn account. We receive information about your visits and interaction with services provided by others when you log-in with LinkedIn or visit others’ services that include some of our plugins (such as “Apply with LinkedIn”) or our ads, cookies or similar technologies. 1.9 Other We are improving our Services, which means we get new data and create new ways to use data. Our Services are dynamic, and we often introduce new features, which may require the collection of new information. If we collect materially different personal data or materially change how we collect, use or share your data, we will notify you and may also modify this Privacy Policy. Key Terms Affiliates Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., GitHub, Inc.). 2. How We Use Your Data We use your data to provide, support, personalize and develop our Services. How we use your personal data will depend on which Services you use, how you use those Services and the choices you make in your settings . We may use your personal data to improve, develop, and provide products and Services, develop and train artificial intelligence (AI) models, develop, provide, and personalize our Services, and gain insights with the help of AI, automated systems, and inferences, so that our Services can be more relevant and useful to you and others. You can review LinkedIn's Responsible AI principles here and learn more about our approach to generative AI here . Learn more about the inferences we may make, including as to your age and gender and how we use them. 2.1 Services Our Services help you connect with others, find and be found for work and business opportunities, stay informed, get training and be more productive. We use your data to authorize access to our Services and honor your settings. Stay Connected Our Services allow you to stay in touch and up to date with colleagues, partners, clients, and other professional contacts. To do so, you can “connect” with the professionals who you choose, and who also wish to “connect” with you. Subject to your and their settings , when you connect with other Members, you will be able to search each others’ connections in order to exchange professional opportunities. We use data about you (such as your profile, profiles you have viewed or data provided through address book uploads or partner integrations) to help others find your profile, suggest connections for you and others (e.g. Members who share your contacts or job experiences) and enable you to invite others to become a Member and connect with you. You can also opt-in to allow us to use your precise location or proximity to others for certain tasks (e.g. to suggest other nearby Members for you to connect with, calculate the commute to a new job, or notify your connections that you are at a professional event). It is your choice whether to invite someone to our Services, send a connection request, or allow another Member to become your connection. When you invite someone to connect with you, your invitation will include your network and basic profile information (e.g., name, profile photo, job title, region). We will send invitation reminders to the person you invited. You can choose whether or not to share your own list of connections with your connections. Visitors have choices about how we use their data. Stay Informed Our Services allow you to stay informed about news, events and ideas regarding professional topics you care about, and from professionals you respect. Our Services also allow you to improve your professional skills, or learn new ones. We use the data we have about you (e.g., data you provide, data we collect from your engagement with our Services and inferences we make from the data we have about you), to personalize our Services for you, such as by recommending or ranking relevant content and conversations on our Services. We also use the data we have about you to suggest skills you could add to your profile and skills that you might need to pursue your next opportunity. So, if you let us know that you are interested in a new skill (e.g., by watching a learning video), we will use this information to personalize content in your feed, suggest that you follow certain Members on our site, or suggest related learning content to help you towards that new skill. We use your content, activity and other data, including your name and photo, to provide notices to your network and others. For example, subject to your settings , we may notify others that you have updated your profile, posted content, took a social action , used a feature, made new connections or were mentioned in the news . Career Our Services allow you to explore careers, evaluate educational opportunities, and seek out, and be found for, career opportunities. Your profile can be found by those looking to hire (for a job or a specific task ) or be hired by you. We will use your data to recommend jobs and show you and others relevant professional contacts (e.g., who work at a company, in an industry, function or location or have certain skills and connections). You can signal that you are interested in changing jobs and share information with recruiters. We will use your data to recommend jobs to you and you to recruiters. We may use automated systems to provide content and recommendations to help make our Services more relevant to our Members, Visitors and customers. Keeping your profile accurate and up-to-date may help you better connect to others and to opportunities through our Services. Productivity Our Services allow you to collaborate with colleagues, search for potential clients, customers, partners and others to do business with. Our Services allow you to communicate with other Members and schedule and prepare meetings with them. If your settings allow, we scan messages to provide “bots” or similar tools that facilitate tasks such as scheduling meetings, drafting responses, summarizing messages or recommending next steps. Learn more . 2.2 Premium Services Our premium Services help paying users to search for and contact Members through our Services, such as searching for and contacting job candidates, sales leads and co-workers, manage talent and promote content. We sell premium Services that provide our customers and subscribers with customized-search functionality and tools (including messaging and activity alerts) as part of our talent, marketing and sales solutions. Customers can export limited information from your profile, such as name, headline, current company, current title, and general location (e.g., Dublin), such as to manage sales leads or talent, unless you opt-out . We do not provide contact information to customers as part of these premium Services without your consent. Premium Services customers can store information they have about you in our premium Services, such as a resume or contact information or sales history. The data stored about you by these customers is subject to the policies of those customers. Other enterprise Services and features that use your data include TeamLink and LinkedIn Pages (e.g., content analytics and followers). 2.3 Communications We contact you and enable communications between Members. We offer settings to control what messages you receive and how often you receive some types of messages. We will contact you through email, mobile phone, notices posted on our websites or apps, messages to your LinkedIn inbox, and other ways through our Services, including text messages and push notifications. We will send you messages about the availability of our Services, security, or other service-related issues. We also send messages about how to use our Services, network updates, reminders, job suggestions and promotional messages from us and our partners. You may change your communication preferences at any time. Please be aware that you cannot opt out of receiving service messages from us, including security and legal notices. We also enable communications between you and others through our Services, including for example invitations , InMail , groups and messages between connections. 2.4 Advertising We serve you tailored ads both on and off our Services. We offer you choices regarding personalized ads, but you cannot opt-out of seeing non-personalized ads. We target (and measure the performance of) ads to Members, Visitors and others both on and off our Services directly or through a variety of partners, using the following data, whether separately or combined: Data collected by advertising technologies on and off our Services using pixels, ad tags (e.g., when an advertiser installs a LinkedIn tag on their website), cookies, and other device identifiers; Member-provided information (e.g., profile, contact information, title and industry); Data from your use of our Services (e.g., search history, feed, content you read, who you follow or is following you, connections, groups participation, page visits, videos you watch, clicking on an ad, etc.), including as described in Section 1.3; Information from advertising partners , vendors and publishers ; and Information inferred from data described above (e.g., using job titles from a profile to infer industry, seniority, and compensation bracket; using graduation dates to infer age or using first names or pronoun usage to infer gender; using your feed activity to infer your interests; or using device data to recognize you as a Member). Learn more about the inferences we make and how they may be used for advertising. Learn more about the ad technologies we use and our advertising services and partners. You can learn more about our compliance with laws in the Designated Countries or the UK in our European Regional Privacy Notice . We will show you ads called sponsored content which look similar to non-sponsored content, except that they are labeled as advertising (e.g., as “ad” or “sponsored”). If you take a social action (such as like, comment or share) on these ads, your action is associated with your name and viewable by others, including the advertiser. Subject to your settings , if you take a social action on the LinkedIn Services, that action may be mentioned with related ads. For example, when you like a company we may include your name and photo when their sponsored content is shown. Ad Choices You have choices regarding our uses of certain categories of data to show you more relevant ads. Member settings can be found here . For Visitors, the setting is here . Info to Ad Providers We do not share your personal data with any non-Affiliated third-party advertisers or ad networks except for: (i) hashed IDs or device identifiers (to the extent they are personal data in some countries); (ii) with your separate permission (e.g., in a lead generation form) or (iii) data already visible to any users of the Services (e.g., profile). However, if you view or click on an ad on or off our Services, the ad provider will get a signal that someone visited the page that displayed the ad, and they may, through the use of mechanisms such as cookies, determine it is you. Advertising partners can associate personal data collected by the advertiser directly from you with hashed IDs or device identifiers received from us. We seek to contractually require such advertising partners to obtain your explicit, opt-in consent before doing so where legally required, and in such instances, we take steps to ensure that consent has been provided before processing data from them. 2.5 Marketing We promote our Services to you and others. In addition to advertising our Services, we use Members’ data and content for invitations and communications promoting membership and network growth, engagement and our Services, such as by showing your connections that you have used a feature on our Services. 2.6 Developing Services and Research We develop our Services and conduct research Service Development We use data, including public feedback, to conduct research and development for our Services in order to provide you and others with a better, more intuitive and personalized experience, drive membership growth and engagement on our Services, and help connect professionals to each other and to economic opportunity. Other Research We seek to create economic opportunity for Members of the global workforce and to help them be more productive and successful. We use the personal data available to us to research social, economic and workplace trends, such as jobs availability and skills needed for these jobs and policies that help bridge the gap in various industries and geographic areas. In some cases, we work with trusted third parties to perform this research, under controls that are designed to protect your privacy. We may also make public data available to researchers to enable assessment of the safety and legal compliance of our Services. We publish or allow others to publish economic insights, presented as aggregated data rather than personal data. Surveys Polls and surveys are conducted by us and others through our Services. You are not obligated to respond to polls or surveys, and you have choices about the information you provide. You may opt-out of survey invitations. 2.7 Customer Support We use data to help you and fix problems. We use data (which can include your communications) to investigate, respond to and resolve complaints and for Service issues (e.g., bugs). 2.8 Insights That Do Not Identify You We use data to generate insights that do not identify you. We use your data to perform analytics to produce and share insights that do not identify you. For example, we may use your data to generate statistics about our Members, their profession or industry, to calculate ad impressions served or clicked on (e.g., for basic business reporting to support billing and budget management or, subject to your settings , for reports to advertisers who may use them to inform their advertising campaigns), to show Members' information about engagement with a post or LinkedIn Page , to publish visitor demographics for a Service or create demographic workforce insights, or to understand usage of our services. 2.9 Security and Investigations We use data for security, fraud prevention and investigations. We and our Affiliates, including Microsoft, may use your data (including your communications) for security purposes or to prevent or investigate possible fraud or other violations of the law, our User Agreement and/or attempts to harm our Members, Visitors, company, Affiliates, or others. Key Terms Social Action E.g. like, comment, follow, share Partners Partners include ad networks, exchanges and others 3. How We Share Information 3.1 Our Services Any data that you include on your profile and any content you post or social action (e.g., likes, follows, comments, shares) you take on our Services will be seen by others, consistent with your settings. Profile Your profile is fully visible to all Members and customers of our Services. Subject to your settings , it can also be visible to others on or off of our Services (e.g., Visitors to our Services or users of third-party search tools). As detailed in our Help Center , your settings, degree of connection with the viewing Member, the subscriptions they may have, their usage of our Services , access channels and search types (e.g., by name or by keyword) impact the availability of your profile and whether they can view certain fields in your profile. Posts, Likes, Follows, Comments, Messages Our Services allow viewing and sharing information including through posts, likes, follows and comments. When you share an article or a post (e.g., an update, image, video or article) publicly it can be viewed by everyone and re-shared anywhere (subject to your settings ). Members, Visitors and others will be able to find and see your publicly-shared content, including your name (and photo if you have provided one). In a group , posts are visible to others according to group type. For example, posts in private groups are visible to others in the group and posts in public groups are visible publicly. Your membership in groups is public and part of your profile, but you can change visibility in your settings . Any information you share through companies’ or other organizations’ pages on our Services will be viewable by those organizations and others who view those pages' content. When you follow a person or organization, you are visible to others and that “page owner” as a follower. We let senders know when you act on their message, subject to your settings where applicable. Subject to your settings , we let a Member know when you view their profile. We also give you choices about letting organizations know when you've viewed their Page. When you like or re-share or comment on another’s content (including ads), others will be able to view these “social actions” and associate it with you (e.g., your name, profile and photo if you provided it). Your employer can see how you use Services they provided for your work (e.g. as a recruiter or sales agent) and related information. We will not show them your job searches or personal messages. Enterprise Accounts Your employer may offer you access to our enterprise Services such as Recruiter, Sales Navigator, LinkedIn Learning or our advertising Campaign Manager. Your employer can review and manage your use of such enterprise Services. Depending on the enterprise Service, before you use such Service, we will ask for permission to share with your employer relevant data from your profile or use of our non-enterprise Services. For example, users of Sales Navigator will be asked to share their “social selling index”, a score calculated in part based on their personal account activity. We understand that certain activities such as job hunting and personal messages are sensitive, and so we do not share those with your employer unless you choose to share it with them through our Services (for example, by applying for a new position in the same company or mentioning your job hunting in a message to a co-worker through our Services). Subject to your settings , when you use workplace tools and services (e.g., interactive employee directory tools) certain of your data may also be made available to your employer or be connected with information we receive from your employer to enable these tools and services. 3.2 Communication Archival Regulated Members may need to store communications outside of our Service. Some Members (or their employers) need, for legal or professional compliance, to archive their communications and social media activity, and will use services of others to provide these archival services. We enable archiving of messages by and to those Members outside of our Services. For example, a financial advisor needs to archive communications with her clients through our Services in order to maintain her professional financial advisor license. 3.3 Others’ Services You may link your account with others’ services so that they can look up your contacts’ profiles, post your shares on such platforms, or enable you to start conversations with your connections on such platforms. Excerpts from your profile will also appear on the services of others. Subject to your settings , other services may look up your profile. When you opt to link your account with other services, personal data (e.g., your name, title, and company) will become available to them. The sharing and use of that personal data will be described in, or linked to, a consent screen when you opt to link the accounts. For example, you may link your Twitter or WeChat account to share content from our Services into these other services, or your email provider may give you the option to upload your LinkedIn contacts into its own service. Third-party services have their own privacy policies, and you may be giving them permission to use your data in ways we would not. You may revoke the link with such accounts. The information you make available to others in our Services (e.g., information from your profile, your posts, your engagement with the posts, or message to Pages) may be available to them on other services . For example, search tools, mail and calendar applications, or talent and lead managers may show a user limited profile data (subject to your settings ), and social media management tools or other platforms may display your posts. The information retained on these services may not reflect updates you make on LinkedIn. 3.4 Related Services We share your data across our different Services and LinkedIn affiliated entities. We will share your personal data with our Affiliates to provide and develop our Services. For example, we may refer a query to Bing in some instances, such as where you'd benefit from a more up to date response in a chat experience. Subject to our European Regional Privacy Notice , we may also share with our Affiliates, including Microsoft, your (1) publicly-shared content (such as your public LinkedIn posts) to provide or develop their services and (2) personal data to improve, provide or develop their advertising services. Where allowed , we may combine information internally across the different Services covered by this Privacy Policy to help our Services be more relevant and useful to you and others. For example, we may personalize your feed or job recommendations based on your learning history. 3.5 Service Providers We may use others to help us with our Services. We use others to help us provide our Services (e.g., maintenance, analysis, audit, payments, fraud detection, customer support, marketing and development). They will have access to your information (e.g., the contents of a customer support request) as reasonably necessary to perform these tasks on our behalf and are obligated not to disclose or use it for other purposes. If you purchase a Service from us, we may use a payments service provider who may separately collect information about you (e.g., for fraud prevention or to comply with legal obligations). 3.6 Legal Disclosures We may need to share your data when we believe it’s required by law or to help protect the rights and safety of you, us or others. It is possible that we will need to disclose information about you when required by law, subpoena, or other legal process or if we have a good faith belief that disclosure is reasonably necessary to (1) investigate, prevent or take action regarding suspected or actual illegal activities or to assist government enforcement agencies; (2) enforce our agreements with you; (3) investigate and defend ourselves against any third-party claims or allegations; (4) protect the security or integrity of our Services or the products or services of our Affiliates (such as by sharing with companies facing similar threats); or (5) exercise or protect the rights and safety of LinkedIn, our Members, personnel or others. We attempt to notify Members about legal demands for their personal data when appropriate in our judgment, unless prohibited by law or court order or when the request is an emergency. We may dispute such demands when we believe, in our discretion, that the requests are overbroad, vague or lack proper authority, but we do not promise to challenge every demand. To learn more see our Data Request Guidelines and Transparency Report . 3.7 Change in Control or Sale We may share your data when our business is sold to others, but it must continue to be used in accordance with this Privacy Policy. We can also share your personal data as part of a sale, merger or change in control, or in preparation for any of these events. Any other entity which buys us or part of our business will have the right to continue to use your data, but only in the manner set out in this Privacy Policy unless you agree otherwise. 4. Your Choices & Obligations 4.1 Data Retention We keep most of your personal data for as long as your account is open. We generally retain your personal data as long as you keep your account open or as needed to provide you Services. This includes data you or others provided to us and data generated or inferred from your use of our Services. Even if you only use our Services when looking for a new job every few years, we will retain your information and keep your profile open, unless you close your account. In some cases we choose to retain certain information (e.g., insights about Services use) in a depersonalized or aggregated form. 4.2 Rights to Access and Control Your Personal Data You can access or delete your personal data. You have many choices about how your data is collected, used and shared. We provide many choices about the collection, use and sharing of your data, from deleting or correcting data you include in your profile and controlling the visibility of your posts to advertising opt-outs and communication controls. We offer you settings to control and manage the personal data we have about you. For personal data that we have about you, you can: Delete Data : You can ask us to erase or delete all or some of your personal data (e.g., if it is no longer necessary to provide Services to you). Change or Correct Data : You can edit some of your personal data through your account. You can also ask us to change, update or fix your data in certain cases, particularly if it’s inaccurate. Object to, or Limit or Restrict, Use of Data : You can ask us to stop using all or some of your personal data (e.g., if we have no legal right to keep using it) or to limit our use of it (e.g., if your personal data is inaccurate or unlawfully held). Right to Access and/or Take Your Data : You can ask us for a copy of your personal data and can ask for a copy of personal data you provided in machine readable form. Visitors can learn more about how to make these requests here . You may also contact us using the contact information below, and we will consider your request in accordance with applicable laws. Residents in the Designated Countries and the UK , and other regions , may have additional rights under their laws. 4.3 Account Closure We keep some of your data even after you close your account. If you choose to close your LinkedIn account, your personal data will generally stop being visible to others on our Services within 24 hours. We generally delete closed account information within 30 days of account closure, except as noted below. We retain your personal data even after you have closed your account if reasonably necessary to comply with our legal obligations (including law enforcement requests), meet regulatory requirements, resolve disputes, maintain security, prevent fraud and abuse (e.g., if we have restricted your account for breach of our Professional Community Policies ), enforce our User Agreement, or fulfill your request to "unsubscribe" from further messages from us. We will retain de-personalized information after your account has been closed. Information you have shared with others (e.g., through InMail, updates or group posts) will remain visible after you close your account or delete the information from your own profile or mailbox, and we do not control data that other Members have copied out of our Services. Groups content and ratings or review content associated with closed accounts will show an unknown user as the source. Your profile may continue to be displayed in the services of others (e.g., search tools) until they refresh their cache. 5. Other Important Information 5.1. Security We monitor for and try to prevent security breaches. Please use the security features available through our Services. We implement security safeguards designed to protect your data, such as HTTPS. We regularly monitor our systems for possible vulnerabilities and attacks. However, we cannot warrant the security of any information that you send us. There is no guarantee that data may not be accessed, disclosed, altered, or destroyed by breach of any of our physical, technical, or managerial safeguards. 5.2. Cross-Border Data Transfers We store and use your data outside your country. We process data both inside and outside of the United States and rely on legally-provided mechanisms to lawfully transfer data across borders. Learn more . Countries where we process data may have laws which are different from, and potentially not as protective as, the laws of your own country. 5.3 Lawful Bases for Processing We have lawful bases to collect, use and share data about you. You have choices about our use of your data. At any time, you can withdraw consent you have provided by going to settings. We will only collect and process personal data about you where we have lawful bases. Lawful bases include consent (where you have given consent), contract (where processing is necessary for the performance of a contract with you (e.g., to deliver the LinkedIn Services you have requested) and “legitimate interests.” Learn more . Where we rely on your consent to process personal data, you have the right to withdraw or decline your consent at any time and where we rely on legitimate interests, you have the right to object. Learn More . If you have any questions about the lawful bases upon which we collect and use your personal data, please contact our Data Protection Officer here . If you're located in one of the Designated Countries or the UK, you can learn more about our lawful bases for processing in our European Regional Privacy Notice . 5.4. Direct Marketing and Do Not Track Signals Our statements regarding direct marketing and “do not track” signals. We currently do not share personal data with third parties for their direct marketing purposes without your permission. Learn more about this and about our response to “do not track” signals. 5.5. Contact Information You can contact us or use other options to resolve any complaints. If you have questions or complaints regarding this Policy, please first contact LinkedIn online. You can also reach us by physical mail . If contacting us does not resolve your complaint, you have more options . Residents in the Designated Countries and other regions may also have the right to contact our Data Protection Officer here . If this does not resolve your complaint, Residents in the Designated Countries and other regions may have more options under their laws. Key Terms Consent Where we process data based on consent, we will ask for your explicit consent. You may withdraw your consent at any time, but that will not affect the lawfulness of the processing of your personal data prior to such withdrawal. Where we rely on contract, we will ask that you agree to the processing of personal data that is necessary for entering into or performance of your contract with us. We will rely on legitimate interests as a basis for data processing where the processing of your data is not overridden by your interests or fundamental rights and freedoms. LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
https://www.linkedin.com/posts/suprsend_hiring-activity-7404858126669201408-G17E | #hiring | SuprSend Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Register now SuprSend’s Post SuprSend 19,129 followers 1mo Report this post We're #hiring a new UI / UX Designer in Bengaluru, Karnataka. Apply today or share this post with your network. UI / UX Designer SuprSend, Bengaluru, Karnataka, India 7 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in 19,129 followers View Profile Follow Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/sms-template#adding-dynamic-content-in-sms | SMS Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors SMS Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors SMS Template OpenAI Open in ChatGPT How to design and publish SMS template. OpenAI Open in ChatGPT Design Template You can design SMS template on SuprSend with a simple form editor tool. You can add variables with Handlebarsjs language. You can check how the message will look in the preview section on the right side. The SMS template has 3 parts: Message type (Transactional, Promotional, Engagement), Header (template headers added in the SMS integration settings), Body (SMS template is added here). Once designed, you can save the SMS template by clicking on “Save” button. When you are ready, you can Publish Draft by providing a name to the version. This will create a version in ‘Pending Approval’ state. Every SMS template goes through an approval process, where the templates are submitted to the registered DLT portal for review, where the SMS is reviewed based on the DLT guidelines and SMS either gets approved or rejected. SuprSend handles the template approval process for you. All you have to do is create a template on SuprSend while following DLT template guidelines, and wait for the approval / rejection of template. Accordingly, the published template version’s state will move to Live or Rejected . Once the version goes Live , you can use the template to send to your users. SMS fields description Field Description Message Type There are 3 types of message - (1) Transactional - Service implicit or Informative messages which are triggered corresponding to a user’s action either done at the time of sending the message or based on past data. All other OTPs other than bank OTPs also fall in this category. e.g.- delivery updates, E-commerce website OTPs etc. (2) Promotional - All the marketing related messages where we have not taken any explicit consent from the user. e.g.- messages sent to promote or sell a product (3) Engagement - Service Explicit or Engagement messages which are triggered to re-engage the users back to platform like promoting new features and offers. e.g.- new feature promotion, discount offer messages to existing customers etc. Header Header should be registered with DLT. Separate headers would be there for all the message types Body SMS template added here should follow DLT template guidelines. Click here to view all DLT guidelines Please note that to send the SMS, you will need to integrate SMS vendor with SuprSend. Please visit the ‘Vendor Integration Guideline’ section to see vendors list and how to integrate them. Vendor Integration Required 📘 Please note that to send the SMS, you will need to integrate SMS vendor with SuprSend. Please visit the ‘Vendor Integration Guideline’ section to see vendors list and how to integrate them. Adding dynamic content in SMS There will always be the case where you would be required to add dynamic content to a template, so as to personalise it for your users. To achieve this, you can add variables in the template, which will be replaced with the dynamic content at the time of sending email. To send actual values to replace variables at the time of communication trigger, use one of our frontend or backend SDKs. Here is a step by step guide on how to add dynamic content in a template: 1 Declaring Variables in the global 'Mock data' button: If you are at this stage, it is assumed that you have declared the variables along with sample values in the global Mock data button. To see how to declare variables before using them in designing templates, refer to this section in the Templates documentation . 2 Using variables in the templates: Once the variables are declared, you can use them while designing template for any channel. We support handlebarsjs to add variables in the template. As a general rule, all the variables have to be entered within double curly brackets: {{variable\_name}} If you have declared the variables and added sample data in the global Mock data button, then they will come as auto-suggestions when you type a curly bracket { . This will remove the chances of error like variable mismatch at the time of template rendering. Note that you will be able to enter a variable name even when you have not declared it inside the Variables button. To manually enter the variable name, follow the handlerbarsjs guide here . Below are some examples of how to enter variables in the template design. For illustration, we are using the same sample variable names that we declared in the Templates section: json Copy Ask AI { "array" : [ { "product_name" : "Aldo Sling Bag" , "product_price" : "3,950.00" }, { "product_name" : "Clarles & Keith Women Slipper, Biege, 38UK" , "product_price" : "2,549.00" }, { "product_name" : "RayBan Sunglasses" , "product_price" : "7,899.00" } ], "event" : { "location" : { "city" : "Bangalore" , "state" : "KA" }, "order_id" : "11200123" , "first_name" : "Nikita" }, "product_page" : "https://www.suprsend.com" } To enter a nested variable, enter in the format {{var1.var2.var3}} . Eg. to refer to city in the example above, you need to enter {{event.location.city}} If you have any space in the variable name, enclose it in square bracket {{event.[first name]}} To refer to an array element, enter in format {{var1.[index].var2}} . Eg. to refer to product_name of the first element of the array array , enter {{array.[0].product_name}} At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user. Please note that the rest of the templates will be sent. Eg. if there is an error in rendering Android Push template, but SMS template is successfully rendered, Android Push notification will not be triggered, but SMS notification will be triggered by SuprSend. Was this page helpful? Yes No Suggest edits Raise issue Previous Whatsapp Template How to design whatsapp template using form editor. Next ⌘ I x github linkedin youtube Powered by On this page Design Template SMS fields description Adding dynamic content in SMS | 2026-01-13T08:48:25 |
https://www.linkedin.com/products/suprsend/ | SuprSend | LinkedIn Skip to main content LinkedIn SuprSend in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in SuprSend Push Notification Software by SuprSend See who's skilled in this Add as skill Contact us Report this product About SuprSend is a notification infrastructure as a service platform for easily creating, managing, and delivering notifications to your end users. SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack are that: * You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritize vendors and channels from your SuprSend account, * You can design powerful templates for all channels together and manage them from a single place, * You can leverage powerful features to experiment fast with notifications and take care of end-user experience without writing a single line of code. This product is intended for Software Engineer Product Manager Chief Technology Officer Chief Product Officer Software Engineering Manager DevOps Engineer Media Products media viewer No more previous content SuprSend - Dashboard Single place to understand ins and outs of all your communication across vendors & channels Integrate Vendors without writing code Integrate with Email, SMS, Push, Slack, Whatsapp without writing a single line of code. No more next content Featured customers of SuprSend Dhan Financial Services 19,584 followers Freightify Software Development 25,343 followers Delightree Software Development 5,661 followers topmate.io Software Development 120,530 followers Fitmint Wellness and Fitness Services 21,769 followers One World Nation (OWN) Computer Games 5,096 followers Refrens Technology, Information and Internet 6,031 followers Show more Show less Similar products MAS MAS Push Notification Software Batch Batch Push Notification Software PUSH PUSH Push Notification Software Netmera Netmera Push Notification Software MantraNet - Suas consultas ao Siscomex Mantra com mais rapidez e praticidade MantraNet - Suas consultas ao Siscomex Mantra com mais rapidez e praticidade Push Notification Software PushOwl PushOwl Push Notification Software Sign in to see more Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_API/Using_the_Web_Speech_API | Using the Web Speech API - Web APIs | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Web APIs Web Speech API Using the Web Speech API Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 Русский 中文 (简体) Using the Web Speech API The Web Speech API provides two distinct areas of functionality — speech recognition and speech synthesis (also known as text to speech, or TTS) — which open up interesting possibilities for accessibility and control. This article provides an introduction to both the areas, along with demos. In this article Speech recognition On-device speech recognition Contextual biasing in speech recognition Speech synthesis Speech recognition Speech recognition involves receiving audio from a device's microphone (or from an audio track), which is then checked by a speech recognition service. When the service successfully recognizes a word or phrase, it returns a text string (or a list of strings) that you can use to initiate further actions. The Web Speech API has a main controller interface for this — SpeechRecognition — and several related interfaces for representing results. Generally, the speech recognition system available on the user's device is used for the speech recognition. Most modern operating systems have a speech recognition system for issuing voice commands, such as Dictation on macOS or Copilot on Windows. By default, using speech recognition on a web page involves a server-based recognition engine. Your audio is sent to a web service for recognition processing, so it won't work offline. To improve privacy and performance, you can specify that speech recognition be performed on the device. This ensures that neither the audio nor the transcribed speech are sent to a third-party service for processing. We cover the on-device functionality in more detail in the On-device speech recognition section. Demo To demonstrate how to use speech recognition, we've created a sample app called Speech color changer . After you press the Start recognition button, say an HTML color keyword. The app's background color will change to that color. To run the demo, navigate to the live demo URL in a supporting browser . HTML and CSS The HTML and CSS for the app are basic. There's a title, an instruction paragraph ( <p> ), a control <button> , and an output paragraph where we display diagnostic messages, including the words that our app recognized. html <h1>Speech color changer</h1> <p class="hints"></p> <button>Start recognition</button> <p class="output"><em>...diagnostic messages</em></p> The CSS provides a basic responsive styling so that it looks OK across devices. JavaScript Let's look at the JavaScript in a bit more detail. Prefixed properties Some browsers currently support speech recognition with prefixed properties. Therefore, at the start of our code, we include these lines to allow for both prefixed properties and unprefixed versions: js const SpeechRecognition = window.SpeechRecognition || window.webkitSpeechRecognition; const SpeechRecognitionEvent = window.SpeechRecognitionEvent || window.webkitSpeechRecognitionEvent; Color list The next part of our code defines a few sample colors that we print to the UI to give users an idea of what to say: js const colors = [ "aqua", "azure", "beige", "bisque", "black", "blue", "brown", "chocolate", "coral", // … ]; Creating a speech recognition instance Next, we define a speech recognition instance to control the recognition in our app. We do this by using the SpeechRecognition() constructor. js const recognition = new SpeechRecognition(); We then set a few properties of the recognition instance: SpeechRecognition.continuous : Controls whether results are captured continuously ( true ) or only once each time a recognition starts ( false ). SpeechRecognition.lang : Sets the language of the recognition. Setting this explicitly is the recommended best practice. SpeechRecognition.interimResults : Defines whether the speech recognition system should return interim results or only final results. For this demo, final results are good enough. SpeechRecognition.maxAlternatives : Sets the number of alternative potential matches that should be returned per result. This can sometimes be useful, say if a result is not completely clear and you want to display a list of alternatives for the user to choose from. But it's not needed for this demo, so we're just specifying one (which is the default anyway). js recognition.continuous = false; recognition.lang = "en-US"; recognition.interimResults = false; recognition.maxAlternatives = 1; Starting the speech recognition After grabbing references to the output paragraph, the <html> element, the instruction paragraph, and the <button> , we implement an onclick handler. When a user presses the button, the speech recognition service starts by calling SpeechRecognition.start() . We've also used a forEach() method to output colored indicators showing what colors users can try to say. js const diagnostic = document.querySelector(".output"); const bg = document.querySelector("html"); const hints = document.querySelector(".hints"); const startBtn = document.querySelector("button"); const colorHTML = colors .map((v) => `<span style="background-color:${v};">${v}</span>`) .join(""); hints.innerHTML = `Press the button then say a color to change the background color of the app. Try ${colorHTML}.`; startBtn.onclick = () => { recognition.start(); console.log("Ready to receive a color command."); }; Receiving and handling results Once the speech recognition has started, several event handlers become available, which you can use to retrieve results and other related information (see Events for SpeechRecognition ). The most common one is the result event, which fires after a successful result is received: js recognition.onresult = (event) => { const color = event.results[0][0].transcript; diagnostic.textContent = `Result received: ${color}.`; bg.style.backgroundColor = color; console.log(`Confidence: ${event.results[0][0].confidence}`); }; The second line is a bit complex, so we'll explain each part here: The SpeechRecognitionEvent.results property returns a SpeechRecognitionResultList object containing SpeechRecognitionResult objects. It has a getter so it can be accessed like an array — the first [0] returns the SpeechRecognitionResult at position 0 . Each SpeechRecognitionResult object in turn contains SpeechRecognitionAlternative objects, each representing an individual recognized word. These also have getters, so they can be accessed like arrays — the second [0] returns the SpeechRecognitionAlternative at position 0 . The transcript property of the SpeechRecognitionAlternative returns a string containing the recognized text. This value is then used to set the background color to a recognized color and also report it as a diagnostic message in the UI. We also use the speechend event to stop the speech recognition service (using SpeechRecognition.stop() ) after a single word has been recognized: js recognition.onspeechend = () => { recognition.stop(); }; Handling errors and unrecognized speech The last two handlers cover cases where the spoken term isn't recognized or an error occurs with the recognition. The nomatch event is supposed to handle the first case, although in most cases the recognition engine will return something, even if it is unintelligible: js recognition.onnomatch = (event) => { diagnostic.textContent = "I didn't recognize that color."; }; The error event handles cases when there is an actual error with the recognition — the SpeechRecognitionErrorEvent.error property contains the error returned: js recognition.onerror = (event) => { diagnostic.textContent = `Error occurred in recognition: ${event.error}`; }; On-device speech recognition Speech recognition is usually performed using an online service. This means that an audio recording is sent to a server for processing, and the results are then returned to the browser. This has a couple of problems: Privacy: Many users are not comfortable with their speech being sent to a server. Performance: Sending data to a server for every bit of recognition can slow down performance in more intensive applications, and your apps won't work offline. To mitigate these problems, the Web Speech API lets you specify that speech recognition should be handled on-device by the browser. This requires a one-time language pack download for each language you want to recognize; once installed, the functionality will be available offline. This section explains how to use on-device speech recognition. Demo To demonstrate on-device speech recognition, we've created a sample app called On-device speech color changer ( run the demo live ). This demo works in a very similar fashion to the online speech color changer demo discussed earlier, with the differences noted below. Specifying on-device recognition To specify that you want to use the browser's on-device processing, set the SpeechRecognition.processLocally property to true before starting any speech recognition (the default value is false ): js recognition.processLocally = true; Checking availability and installing language packs For on-device speech recognition to work, the browser must have a language pack installed for the language you want to recognize. If you run the start() method after specifying processLocally = true but the correct language pack isn't installed, the function call will fail with a language-not-supported error. To get the correct language pack installed, ensure you follow these two steps: Check whether the language pack is available on the user's device: This is handled using the SpeechRecognition.available() static method. Install the language pack if it isn't available: This is handled using the SpeechRecognition.install() static method. These steps are handled in the following click event handler on the app's control <button> : js startBtn.addEventListener("click", () => { // check availability of target language SpeechRecognition.available({ langs: ["en-US"], processLocally: true }).then( (result) => { if (result === "unavailable") { diagnostic.textContent = `en-US is not available to download at this time. Sorry!`; } else if (result === "available") { recognition.start(); console.log("Ready to receive a color command."); } else { diagnostic.textContent = `en-US language pack is downloading...`; SpeechRecognition.install({ langs: ["en-US"], processLocally: true, }).then((result) => { if (result) { diagnostic.textContent = `en-US language pack downloaded. Start recognition again.`; } else { diagnostic.textContent = `en-US language pack failed to download. Try again later.`; } }); } }, ); }); The available() method takes an options object containing two properties: A langs array containing the languages to check availability for. A processLocally boolean specifying whether to check for the availability of the language only on-device ( true ) or either locally or via a server-based recognition service ( false , the default). When run, this method returns a Promise that resolves with an enumerated value indicating the availability of the specified languages. In our demo, we test for three conditions: If the resulting value is unavailable , it means that no suitable language pack is available to download. We also print an appropriate message to the output. If the resulting value is available , it means that the language pack is available locally, so recognition can begin. In this case, we run start() and log a message to the console when the app is ready to receive speech. If the value is something else ( downloadable or downloading ), we print a diagnostic message to inform the user that a language pack download is starting, then run the install() method to handle the download. The install() method works in a similar way to the available() method, except that its options object only takes the langs array. When run, it starts downloading all the language packs for the languages indicated in langs and returns a Promise that resolves with a boolean indicating whether the specified language packs were downloaded and installed successfully ( true ) or not ( false ). For this demo, we print a diagnostic message to indicate the success and failure cases. In a more complete app, you'd probably disable the controls during the download process and enable them again after the promise resolves. Permissions-policy integration The use of the available() and install() methods is controlled by the on-device-speech-recognition Permissions-Policy . Specifically, where a defined policy blocks usage, any attempts to call these methods will fail. The default allowlist value for on-device-speech-recognition is self . This means you don't need to worry about adjusting the policy unless you're attempting to use these methods in embedded cross-origin documents or want to explicitly disable their use. Unprefixed Web Speech API In the original speech color changer demo, we included extra lines to handle browsers that support the Web Speech API only with vendor-prefixed properties (see the Prefixed properties section for more details). In the on-device version of the demo, prefix-handling code is not needed because the implementations that support this functionality do so without prefixes. Contextual biasing in speech recognition There will be times when a speech recognition service will fail to correctly recognize a specific word or phrase. This most often happens with domain-specific terms (such as medical or scientific vocabulary), proper nouns, uncommon phrases, or words that sound similar to other words and so may be misidentified. For example, during testing, we found that our On-device speech color changer had trouble recognizing the color azure — it kept returning results like "as you". Other colors that were frequently misidentified included khaki ("car key"), tan , and thistle ("this all"). To mitigate such problems, the Web Speech API lets you provide hints to the recognition engine to highlight phrases that are more likely to be spoken and which the engine should be biased towards. This makes those words and phrases more likely to be recognized correctly. You can do this by setting an array of SpeechRecognitionPhrase objects as the value of the SpeechRecognition.phrases property. Each SpeechRecognitionPhrase object contains: A phrase property, which is a string containing the word or phrase you want to boost. A boost property, which is a floating point number between 0.0 and 10.0 (inclusive) that sets the amount of boost you want to apply to that word or phrase. Higher values make the word or phrase more likely to be recognized. In our "On-device speech color changer" demo, we handle this by creating an array of phrases to boost and their boost values: js const phraseData = [ { phrase: "azure", boost: 5.0 }, { phrase: "khaki", boost: 3.0 }, { phrase: "tan", boost: 2.0 }, ]; These need to be represented as an ObservableArray of SpeechRecognitionPhrase objects. We handle this by mapping the original array to convert each array element into a SpeechRecognitionPhrase object using the SpeechRecognitionPhrase() constructor: js const phraseObjects = phraseData.map( (p) => new SpeechRecognitionPhrase(p.phrase, p.boost), ); After creating the SpeechRecognition instance, we add our contextual biasing phrases by setting the phraseObjects array as the value of the SpeechRecognition.phrases property: js recognition.phrases = phraseObjects; The phrases array can be modified just like a normal JavaScript array, for example by pushing new phrases to it dynamically: js recognition.phrases.push(new SpeechRecognitionPhrase("thistle", 5.0)); With this code, we found that the problematic color keywords were recognized more accurately than before. Speech synthesis Speech synthesis (aka text-to-speech, or TTS) involves receiving synthesizing text contained within an app to speech, and playing it out of a device's speaker or audio output connection. The Web Speech API has a main controller interface for this — SpeechSynthesis — plus a number of closely-related interfaces for representing text to be synthesized (known as utterances), voices to be used for the utterance, etc. Again, most OSes have some kind of speech synthesis system, which will be used by the API for this task as available. Demo To demonstrate how to use web speech synthesis, we've created a sample app called Speech synthesizer . It has an input field for entering the text to be synthesized. You can adjust the rate and pitch and also select a voice from the dropdown menu to use for the spoken text. After you've entered your text, press Enter / Return or click the Play button to hear the text read aloud. To run the demo, navigate to the live demo URL in a supporting browser . HTML and CSS The HTML and CSS for this app are pretty basic. There's a title, some instructions for use, and a form with some basic controls. The <select> element is initially empty; it is populated with <option> s via JavaScript (covered later). html <h1>Speech synthesizer</h1> <p> Enter some text in the input below and press return to hear it. Change voices using the dropdown menu. </p> <form> <input type="text" class="txt" /> <div> <label for="rate">Rate</label ><input type="range" min="0.5" max="2" value="1" step="0.1" id="rate" /> <div class="rate-value">1</div> <div class="clearfix"></div> </div> <div> <label for="pitch">Pitch</label ><input type="range" min="0" max="2" value="1" step="0.1" id="pitch" /> <div class="pitch-value">1</div> <div class="clearfix"></div> </div> <select></select> </form> JavaScript Let's investigate the JavaScript that powers this app. Setting variables First of all, we capture references to all the DOM elements involved in the UI, but more interestingly, we capture a reference to Window.speechSynthesis . This is API's entry point — it returns an instance of SpeechSynthesis , the controller interface for web speech synthesis. js const synth = window.speechSynthesis; const inputForm = document.querySelector("form"); const inputTxt = document.querySelector(".txt"); const voiceSelect = document.querySelector("select"); const pitch = document.querySelector("#pitch"); const pitchValue = document.querySelector(".pitch-value"); const rate = document.querySelector("#rate"); const rateValue = document.querySelector(".rate-value"); const voices = []; Populating the select element To populate the <select> element with the different voice options the device has available, we've written a populateVoiceList() function. We first invoke SpeechSynthesis.getVoices() , which returns a list of all the available voices, represented by SpeechSynthesisVoice objects. We then loop through this list — for each voice we create an <option> element, set its text content to display the name of the voice (grabbed from SpeechSynthesisVoice.name ), the language of the voice (grabbed from SpeechSynthesisVoice.lang ), and -- DEFAULT if the voice is the default voice for the synthesis engine (checked by seeing if SpeechSynthesisVoice.default returns true .) We also create data- attributes for each option, containing the name and language of the associated voice, so we can grab them easily later on, and then append the options as children of the select. js function populateVoiceList() { voices = synth.getVoices(); for (const voice of voices) { const option = document.createElement("option"); option.textContent = `${voice.name} (${voice.lang})`; if (voice.default) { option.textContent += " — DEFAULT"; } option.setAttribute("data-lang", voice.lang); option.setAttribute("data-name", voice.name); voiceSelect.appendChild(option); } } Older browser don't support the voiceschanged event, and just return a list of voices when SpeechSynthesis.getVoices() is fired. While on others, such as Chrome, you have to wait for the event to fire before populating the list. To allow for both cases, we run the function as shown below: js populateVoiceList(); if (speechSynthesis.onvoiceschanged !== undefined) { speechSynthesis.onvoiceschanged = populateVoiceList; } Speaking the entered text Next, we create an event handler to start speaking the text entered into the text field. We are using an onsubmit handler on the form so that the action happens when Enter / Return is pressed. We first create a new SpeechSynthesisUtterance() instance using its constructor — this is passed the text input's value as a parameter. Next, we need to figure out which voice to use. We use the HTMLSelectElement selectedOptions property to return the currently selected <option> element. We then use this element's data-name attribute, finding the SpeechSynthesisVoice object whose name matches this attribute's value. We set the matching voice object to be the value of the SpeechSynthesisUtterance.voice property. Finally, we set the SpeechSynthesisUtterance.pitch and SpeechSynthesisUtterance.rate to the values of the relevant range form elements. Then, with all necessary preparations made, we start the utterance being spoken by invoking SpeechSynthesis.speak() , passing it the SpeechSynthesisUtterance instance as a parameter. js inputForm.onsubmit = (event) => { event.preventDefault(); const utterThis = new SpeechSynthesisUtterance(inputTxt.value); const selectedOption = voiceSelect.selectedOptions[0].getAttribute("data-name"); for (const voice of voices) { if (voice.name === selectedOption) { utterThis.voice = voice; } } utterThis.pitch = pitch.value; utterThis.rate = rate.value; synth.speak(utterThis); utterThis.onpause = (event) => { const char = event.utterance.text.charAt(event.charIndex); console.log( `Speech paused at character ${event.charIndex} of "${event.utterance.text}", which is "${char}".`, ); }; inputTxt.blur(); }; In the final part of the handler, we include a pause event to demonstrate how SpeechSynthesisEvent can be put to good use. When SpeechSynthesis.pause() is invoked, this returns a message reporting the character number and name that the speech was paused at. Finally, we call blur() on the text input. This is mainly to hide the keyboard on Firefox OS. Updating the displayed pitch and rate values The last part of the code updates the pitch / rate values displayed in the UI, each time the slider positions are moved. js pitch.onchange = () => { pitchValue.textContent = pitch.value; }; rate.onchange = () => { rateValue.textContent = rate.value; }; Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Oct 7, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Web Speech API Guides Using the Web Speech API Interfaces SpeechGrammar Deprecated SpeechGrammarList Deprecated SpeechRecognition SpeechRecognitionAlternative SpeechRecognitionErrorEvent SpeechRecognitionEvent SpeechRecognitionPhrase Experimental SpeechRecognitionResult SpeechRecognitionResultList SpeechSynthesis SpeechSynthesisErrorEvent SpeechSynthesisEvent SpeechSynthesisUtterance SpeechSynthesisVoice Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://dev.to/leena_malhotra/why-asking-for-better-outputs-misses-the-real-problem-29f9#sd35-mediums-averaging-problem | Why Asking for Better Outputs Misses the Real Problem - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Leena Malhotra Posted on Jan 12 Why Asking for Better Outputs Misses the Real Problem # programming # ai # imagegen # nanobanana Yesterday, I spent four hours debugging why Ideogram V3 kept generating inconsistent architectural renders. The whitepaper promised "improved spatial coherence." My outputs looked like they were designed by committee. This isn't a model problem. It's a workflow problem. When Ideogram V3's Whitepaper Met Reality I was building a pipeline to generate interior design variations for an e-commerce platform. The whitepaper showed beautiful examples of architectural spaces with perfect lighting. Here's the prompt I used from their examples: "Modern minimalist living room, floor-to-ceiling windows, natural light, Scandinavian furniture, architectural photography" Enter fullscreen mode Exit fullscreen mode First three generations: perfect. Fourth one: furniture floating off the ground. Fifth: window placement changed. By the tenth iteration, I had seven different room layouts. Same seed, same parameters, same model version. The issue wasn't randomness—it was me treating each generation as independent. The whitepaper examples worked because they were single, carefully-constructed prompts. I was running iterative experiments without maintaining state. The fix: class PromptContext : def __init__ ( self , base_intent ): self . base_intent = base_intent self . style_locks = {} def generate_with_memory ( self , variation ): locked = " " . join ([ f " { k } : { v } " for k , v in self . style_locks . items ()]) return f " { self . base_intent } . { locked } . { variation } " context = PromptContext ( " Modern minimalist living room " ) context . style_locks [ " windows " ] = " floor-to-ceiling on north wall " context . style_locks [ " floor " ] = " light oak hardwood " Enter fullscreen mode Exit fullscreen mode Cost: 40% more tokens per request. Benefit: went from 60% usable outputs to 95%. The whitepaper shows capability, not workflow. When you can test the same prompt across multiple AI models , the dissonance between documentation and reality becomes measurable rather than frustrating. SD3.5 Medium's Averaging Problem I needed product packaging concepts that felt "premium but approachable" for a beverage brand. The brief: Japanese minimalism meets 1970s American optimism. First attempt: { " prompt " : " Premium beverage packaging, minimalist, warm nostalgic colors, sophisticated " , " cfg_scale " : 7.5 , " sampler " : " DPM++ 2M Karras " } Enter fullscreen mode Exit fullscreen mode Result: generic wellness brand aesthetics. Technically perfect. Strategically useless. I ran 50 variations testing cfg_scale from 5.0 to 12.0: cfg_scale=5.0 → Lost brand identity cfg_scale=7.5 → Safe, averaged aesthetics cfg_scale=10.0 → Interesting tensions emerged cfg_scale=12.0 → Overcooked, but committed Enter fullscreen mode Exit fullscreen mode The fix: Stop describing the middle ground. Describe the extremes. prompt_a = " 1970s American optimism, warm oranges, rounded typography, sunburst graphics " prompt_b = " Japanese minimalism, white space, geometric precision " # Generate separately at cfg_scale=11.0 # Then synthesize specific elements Enter fullscreen mode Exit fullscreen mode SD3.5 Medium optimizes for "nothing broken" with vague targets. Give it contradictory specifics and higher CFG, and you get interesting failures to work with. Three unusable images and one brilliant image beats ten mediocre ones. Trade-off: 3x generation time. But revision time savings made it worth it. When Nano Banana PRO New Silently Changed Three-month-old content pipeline. Generated weekly newsletter summaries. Worked fine. One Monday: every output was 40% shorter and weirdly formal. Before (v1.2): 480 tokens, conversational. After (v1.3): 310 tokens, corporate. Release notes: "improved efficiency and coherence." No mention of temperature rescaling. The diff script I now run: def model_regression_test ( old_model , new_model , test_prompts ): results = [] for prompt in test_prompts : old_response = generate ( old_model , prompt , temp = 0.7 ) new_response = generate ( new_model , prompt , temp = 0.7 ) diff = { " length_delta " : len ( new_response ) - len ( old_response ), " formality_delta " : analyze_formality ( new_response ) - analyze_formality ( old_response ) } if abs ( diff [ " length_delta " ]) > 100 : print ( f " WARNING: Length shift " ) results . append ( diff ) return results Enter fullscreen mode Exit fullscreen mode The actual issue: they changed temperature scaling. temp=0.7 in v1.3 behaved like temp=0.4 in v1.2. My fix: pin model versions in production, regression test before upgrading. # requirements.txt nano-banana-pro==1.2.8 # Regression test before upgrade Enter fullscreen mode Exit fullscreen mode "Improved" means "different." Treat model updates like database migrations. Running parallel tests across Nano Banana PRO New and legacy versions reveals what release notes hide. The Context Switching Tax My workflow last month: Draft prompt in ChatGPT Test in Jupyter notebook Check results in Notion Discuss in Slack Update Google Doc Re-run notebook Forget step 1 decisions I was generating legal disclaimer variations. Each category needed specific regulatory language. I'd test in ChatGPT, worked great. Copy to notebook, different results. Thirty minutes debugging before realizing different model versions. The system I built: class ExperimentLog : def __init__ ( self ): self . conn = sqlite3 . connect ( " experiments.db " ) self . setup_db () def log ( self , model , prompt , params , output , success , notes = "" ): self . conn . execute ( """ INSERT INTO experiments (timestamp, model, prompt, parameters, output, success) VALUES (?, ?, ?, ?, ?, ?) """ , ( datetime . now (). isoformat (), model , prompt , json . dumps ( params ), output [: 500 ], success )) def get_successful_prompts ( self , model ): return self . conn . execute ( """ SELECT prompt, parameters FROM experiments WHERE model = ? AND success = 1 ORDER BY timestamp DESC """ , ( model ,)). fetchall () Enter fullscreen mode Exit fullscreen mode Now I search "legal disclaimers last week" and get exact parameters, model version, output. No re-discovering. Context switching isn't just a productivity tax—it fragments intent into micro-decisions scattered across tools. The Long Document Problem 140-page RFP. Needed specific technical requirements. Cross-references, tables, nested appendices. Tried: upload to ChatGPT, ask questions. Me: "What are data retention requirements in Section 7?" ChatGPT: "The document mentions retention in multiple sections..." Me: "No, I need specific retention periods." ChatGPT: "Based on the document, periods vary by type..." Enter fullscreen mode Exit fullscreen mode Summaries of summaries. Never the actual spec. The workflow: def chunk_document ( pdf_path , chunk_size = 4000 ): reader = pypdf . PdfReader ( pdf_path ) chunks = [] for i , page in enumerate ( reader . pages ): text = page . extract_text () words = text . split () for start in range ( 0 , len ( words ), chunk_size - 200 ): chunks . append ({ " page " : i + 1 , " text " : " " . join ( words [ start : start + chunk_size ]) }) return chunks def extract_requirements ( pdf_path ): chunks = chunk_document ( pdf_path ) requirements = [] for chunk in chunks : prompt = f """ Extract technical requirements from: Page { chunk [ ' page ' ] } : { chunk [ ' text ' ] } Return JSON: {{ " requirements " : [{{ " type " : " retention " , " spec " : " 7 years " , " section " : " 7.3.2 " }}]}} """ result = call_llm_api ( prompt ) requirements . extend ( result . get ( " requirements " , [])) return requirements Enter fullscreen mode Exit fullscreen mode Output: [ { "type" : "retention" , "spec" : "7 years for financial records" , "section" : "7.3.2" , "page" : 45 }, { "type" : "retention" , "spec" : "3 years for operational logs" , "section" : "7.3.2" , "page" : 45 } ] Enter fullscreen mode Exit fullscreen mode Trade-off: more processing time and API costs. But went from 3 hours frustrated questioning to 20 minutes automated extraction. Research papers that took hours to read now take minutes with a Document Summarizer . What I'd Do Differently Starting over, I'd version everything. Git for prompts, not just code. Build logging first—wasted weeks re-discovering experiments. Test edge cases, not happy paths. The whitepaper examples are optimized demos. Automate diffs and treat model updates like schema migrations. This is still evolving. If you've hit similar workflow issues, drop a comment. -Leena:) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Leena Malhotra Follow Creator and strategist blending machine learning, business, and creativity. Harvard Business School ’06. Writing about AI, productivity, and building systems for a self-directed life. Location California, United states Education Harvard Business School Joined Jun 17, 2025 More from Leena Malhotra AI Explains Code Well Until the Moment Context Actually Matters # webdev # programming # ai Using AI in Production Code Without Creating Invisible Bugs # webdev # programming # ai Ship Faster, Break Less: My Rules for Using AI Safely in Codebases # webdev # programming # ai # coding 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/react-events-and-user-methods | Events and User methods - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK SuprSend Client SDK Authentication Javascript Android iOS React Native Flutter React SDK Integration WebPush Preferences Events and User methods InApp Feed Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation React Events and User methods Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog React Events and User methods OpenAI Open in ChatGPT Methods to send event or manage user updates based on user action in react-based websites. OpenAI Open in ChatGPT 1 Integrate SuprSendProvider Integrate SuprSendProvider as it is needed for creating SuprSend Client and authenticating user. 2 Call useSuprSendClient hook to access client instance Call useSuprSendClient hook in your react component code to get SuprSend client instance which has all event and user update methods. 3 Call track and user update methods. Please refer these sections to call events and user update methods in your react application, as integration steps are same for both the web-sdk and react-sdk. Was this page helpful? Yes No Suggest edits Raise issue Previous Popover feed Guide to add In-App Popover feed in react-based websites using drop-in components. Next ⌘ I x github linkedin youtube Powered by | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/developer/rest-api | REST API - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation SDKs and APIs REST API Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog SDKs and APIs REST API OpenAI Open in ChatGPT Learn how to use SuprSend REST APIs to sync users and send notifications at scale. OpenAI Open in ChatGPT The SuprSend REST API enables you to sync user data and send notifications at scale. We have SDKs for most popular languages. If your backend or frontend is built in another language or you prefer direct integration, you can use the REST API to programmatically interact with SuprSend. Authentication REST APIs require an API Key for authentication. API Keys are scoped per workspace (e.g., Sandbox, Staging, Production), ensuring isolation across environments. Include your API Key in the Authorization header as a Bearer token: Copy Ask AI Authorization : Bearer <YOUR_API_KEY> Content-Type : application/json API Reference For a complete list of endpoints and request/response schemas, see the API Reference . Postman Collection The fastest way to get started is by exploring the APIs in our Postman Collection . Was this page helpful? Yes No Suggest edits Raise issue Previous Postman Collection Explore and test SuprSend APIs using the official Postman collection, pre-configured with requests and examples. Next ⌘ I x github linkedin youtube Powered by On this page Authentication API Reference Postman Collection | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/ios-push-template#ios-push-notification-fields-description | iOS Push Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors iOS Push Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors iOS Push Template OpenAI Open in ChatGPT How to design simple iOS Push template with click action and image. OpenAI Open in ChatGPT Design Template You can design template with a simple form editor tool. You can add variables with Handlebarsjs language. You can check how the message will look in the preview section on the right side. Once designed, you can save the push notification template by clicking on Save Draft. When you are ready, you can Publish Draft by providing a name to the version. This will become the Live version, and will be used whenever the associated workflow is triggered. iOS Push notification fields description Field Description Title Small message text box. Note that this field will be displayed in single line only, and very long content can get curtailed. Use handlebarsjs to add variables. Body Large message text box. Use handlebarsjs to add variables. 📘 Note: By default, Clicking on the Notification will redirect the users to your iOS App. We’ll be soon be adding the option to add custom Action URL Adding dynamic content in iOS Push There will always be the case where you would require to add dynamic content to a template, so as to personalise it for your users. To achieve this, you can add variables in the template, which will be replaced with the dynamic content at the time of sending the message. You’ll need to pass these while triggering the communication from one of our frontend or backend SDKs. Here is a step-by-step guide on how to add dynamic content in iOS Push: 1 Declaring Variables in the global `Mock data` button If you are at this stage, it is assumed that you have declared the variables along with sample values in the global Mock data button. To see how to declare variables before using them in designing templates, refer to this section in the Templates documentation . 2 Using variables in the templates Once the variables are declared, you can use them while designing the iOS Push template. We support handlebarsjs to add variables in the template. As a general rule, all the variables have to be entered within double curly brackets: {{variable\_name}} If you have declared the variables in the global Mock data button, then they will come as auto-suggestions when you type a curly bracket { . This will remove the chances of errors like variable mismatch at the time of template rendering. Note that you will be able to enter a variable name even when you have not declared it inside the Mock data button. To manually enter the variable name, follow the handlerbarsjs guide here . Below is an example of how to enter variables in the template design. For illustration, we are using the same sample variable names that we declared in the Templates section: json Copy Ask AI { "array" : [ { "product_name" : "Aldo Sling Bag" , "product_price" : "3,950.00" }, { "product_name" : "Clarles & Keith Women Slipper, Biege, 38UK" , "product_price" : "2,549.00" }, { "product_name" : "RayBan Sunglasses" , "product_price" : "7,899.00" } ], "event" : { "location" : { "city" : "San Francisco" , "state" : "California" }, "order_id" : "11200123" , "first_name" : "Joe" }, "product_page" : "https://www.suprsend.com" } To enter a nested variable, enter in the format {{var1.var2.var3}} . E.g. to refer to city in the example above, you need to enter {{event.location.city}} To refer to an array element, enter in format {{var1.[*index*].var2}}. E.g. to refer to product_name of the first element of the array array , enter {{array.[0].product_name}}` If you have any space in the variable name, enclose it in square bracket {{event.[first name]}} You will be able to see the sample values in the Preview section, as well as in the Live version when you publish a draft. If you cannot see your variable being rendered with the sample value, check one of the following: Make sure you have entered the variable name and the sample value in the Mock data button. Make sure you have entered the correct variable name in the template, as per the handlebarsjs guideline. What happens if there is variable mismatch at the time of sending? At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user. Please note that the rest of the templates will be sent. E.g. if there is an error in rendering iOS Push template, but email template is successfully rendered, iOS Push notification will not be triggered, but email notification will be triggered by SuprSend. Was this page helpful? Yes No Suggest edits Raise issue Previous Web Push Template How to design Webpush template with customisation options to add action buttons and image. Next ⌘ I x github linkedin youtube Powered by On this page Design Template iOS Push notification fields description Adding dynamic content in iOS Push | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/developer/postman-collection | Postman Collection - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation SDKs and APIs Postman Collection Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog SDKs and APIs Postman Collection OpenAI Open in ChatGPT Explore and test SuprSend APIs using the official Postman collection, pre-configured with requests and examples. OpenAI Open in ChatGPT Our Postman collection is the fastest way to get familiar with SuprSend APIs. It includes pre-configured requests and example payloads so you can start testing right away. Set Up Postman Collection 1 Fork the collection Go to the SuprSend Postman Workspace and fork the collection into your own workspace. 2 Create environment variables In Postman, create a new environment and add the following variables. Retrieve your credentials from: SuprSend Dashboard → Developers → API Keys SuprSend Dashboard → Account Settings → Service Tokens Variable Description Example Value base_url Base URL for REST API requests https://hub.suprsend.com management_api_base_url Base URL for Management API requests https://management-api.suprsend.com api_key API Key for the respective workspace (REST API auth) your_api_key_here service_token Service Token for account-level Management API auth your_service_token_here 3 Start testing Select the configured environment and start testing SuprSend APIs using the pre-configured requests in the collection. Best Practices Keep your api_key and service_token secure — never share them in a public collection. Use separate environments for Sandbox, Staging, and Production. Rotate credentials periodically following key and token management best practices . Was this page helpful? Yes No Suggest edits Raise issue Previous Validate Trigger Payload Validate the data passed to workflow API or event properties using JSON schemas to catch payload mismatch errors at API level. Next ⌘ I x github linkedin youtube Powered by On this page Set Up Postman Collection Best Practices | 2026-01-13T08:48:25 |
https://www.linkedin.com/posts/suprsend_%F0%9D%97%9B%F0%9D%97%BC%F0%9D%98%84-%F0%9D%97%96%F0%9D%97%BF%F0%9D%97%AE%F0%9D%98%87%F0%9D%98%86%F0%9D%97%9A%F0%9D%97%AE%F0%9D%97%BA%F0%9D%97%B2%F0%9D%98%80-%F0%9D%97%96%F0%9D%98%82%F0%9D%98%81-%F0%9D%97%A1%F0%9D%97%BC%F0%9D%98%81-activity-7401647123265388544-5LjW | CrazyGames Cuts Notification Development Time from Weeks to Hours with SuprSend | SuprSend posted on the topic | LinkedIn Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Register now CrazyGames Cuts Notification Development Time from Weeks to Hours with SuprSend This title was summarized by AI from the post below. SuprSend 19,129 followers 1mo Report this post 𝗛𝗼𝘄 𝗖𝗿𝗮𝘇𝘆𝗚𝗮𝗺𝗲𝘀 𝗖𝘂𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗳𝗿𝗼𝗺 𝗪𝗲𝗲𝗸𝘀 𝘁𝗼 𝗛𝗼𝘂𝗿𝘀 CrazyGames serves 45M+ monthly players across 3,000+ browser games. But their in-house notification system held them back. 🎮 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: Building notifications required heavy engineering involvement. Even small template changes meant creating dev tickets and took 2 weeks to deploy. Product teams couldn't personalize or experiment fast without developer time. 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱: CrazyGames adopted SuprSend to abstract notification development out of code. Templates, logic, and workflows shifted entirely to Product & Design. They also connected their database to SuprSend, allowing teams to create targeted cohorts by writing SQL — no data exports, no syncing delays, no engineering bottlenecks. 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁: • Notification launches: weeks → hours • Self-serve campaigns with personalized game recommendations • A/B testing across email, push, and in-app — all unified • Product teams operate independently 🎥 Watch Jonas (VP of Product, CrazyGames) full story link in comments below. 33 4 Comments Like Comment Share Copy LinkedIn Facebook X SuprSend 1mo Report this comment 📖 Read the case study: https://www.suprsend.com/customers/how-crazygames-boosted-player-engagement-and-developer-retention-with-suprsend Like Reply 2 Reactions 3 Reactions SuprSend 1mo Report this comment 🎥 Watch Full Story: https://youtu.be/Mwp8jmZoPko?si=auMmLp_ngFYxjmw6 Like Reply 2 Reactions 3 Reactions CrazyGames 1mo Report this comment A pleasure working with you! Like Reply 5 Reactions 6 Reactions Yurii Husak 1mo Report this comment I wonder why ot took you 2 weeks for a tweak 🤔 Like Reply 1 Reaction See more comments To view or add a comment, sign in More Relevant Posts Muhammad Hassan Raza 2w Report this post This mobile game didn’t “just work”. I engineered it to scale. 👇 🍽️ Idle Restaurant Tycoon: Match-3 📱 Live on Google Play → https://lnkd.in/dbKFN-7R Most people see: ➡️ fun gameplay ➡️ smooth animations ➡️ addictive progression What they don’t see is what I personally built underneath 👀 ⚙️ Architecture (My Work) • Implemented Zenject DI so features don’t fight each other • Built UniRx reactive flows for UI, game state & async events • Zero spaghetti. Systems talk — not shout. 📊 Live Game Tuning (No Rebuilds) • Connected Google Sheets → JSON → Runtime configs • Economy, prices, timers tuned live while players play • Enabled designers to ship balance changes independently 🧩 Idle × Match-3 Systems • Match-3 results feed idle economy (not fake rewards) • Scalable progression curves (early hook → long tail) • Designed for player retention, not screenshots 🚀 Performance & Optimization • Object pooling, async loading, GC control • Optimized UI redraws & update loops • Tested on low-end Android — still smooth 🌍 Production & Collaboration • Worked with international designers & producers • Turned GDDs into systems that survive live ops • Built QA/debug tools so crashes aren’t “edge cases” This wasn’t a portfolio toy — it’s a shipped, live, data-driven game I personally helped bring to life. If you’re building games and want someone who: ✔️ thinks in systems ✔️ ships under pressure ✔️ writes code meant to live for years Let’s talk. 🎮 Demo / architecture walkthrough → DM #UnityDeveloper #GameDev #GameDeveloper #Unity3D #MobileGames #IdleGames #Match3 #Zenject #UniRx #GameArchitecture #Optimization #Performance #MobileGameDev #IndieDev #ShippedGames #GameSystems #GDD #LiveOps #RemoteJobs #RemoteUnityDeveloper #RemoteGameDeveloper #PakistanJobs #IslamabadJobs #LahoreJobs #GameDevPakistan #GameDevIslamabad #GameDevLahore #UnityJobs #UnityDeveloperPakistan #UnityRemoteJobs #OpenToWork #GameDevCommunity #Unity3DDeveloper #GamingIndustry #TechJobs #SoftwareEngineer …more 35 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Keshavinfotech 1,061 followers 1w Report this post Building high-quality games used to take forever, but things have completely changed in 2026. By combining the latest Unity AI tools with ready-to-use assets, we can now launch games much faster and with a better return on investment, all while keeping that "human touch" that makes a game great. Here is how we are speeding up the process: - Smart Coding: We use AI tools like GitHub Copilot and the Unity AI Assistant to handle the repetitive parts of coding. This lets us focus more on fun gameplay and cuts down development time by nearly 40%. - Quick Visuals: Tools like Meshy AI and Leonardo.ai allow us to create 3D models and 2D art in minutes instead of weeks. We can even generate textures and sounds directly inside the project. - Easier World Building: Instead of placing every tiny object by hand, we use tools like Promethean AI to help design massive, immersive environments quickly. - Lifelike Characters: With tools like Inworld, game characters can now have real conversations with players, making the world feel much more alive. For clients, this is a huge win. It means faster prototypes, lower costs (around 20-30% less overhead), and the ability to build bigger, better worlds on the same budget. We don't reinvent the wheel; we use the best tech available to make sure your game is unique and ready for the market. Is your game idea ready for the 2026 tech stack? Let's build something extraordinary. www.KeshavInfotech.com #JavaScriptShorthand #Mastery 🔥 #html #css #javascript #100daysofcode #webdevelopment #programming #innovation #management #digitalmarketing #technology #creativity #futurism #startups #marketing #socialmedia #socialnetworking #motivation #personaldevelopment #jobinterviews #sustainability #personalbranding #frontend #backend #developer #coding #webdeveloper #webdesign #frontenddeveloper #code #programmer #coder #webdev #web #python #java #php #codinglife #reactjs #softwaredeveloper #development #js #fullstack #software #dev #developers #ui #linkedin #instagram #facebook #twitter #business #youtube #socialmediamarketing #linkedinprofile #google #linkedintips #b #linkedinmarketing #jobsearch #pinterest #seo #resume #Dzirmal #entrepreneur #career #cv #networking #branding #tiktok #linkedinlife #n #jobs #fullstackdeveloper #javascriptdeveloper #daysofcode #webdevelopers #developerlife #peoplewhocode #devlife #learntocode #computerscience #frontenddev #coderlife #programmers #programmerlife #codingisfun #softwareengineer #programmerslife #frontenddevelopment #coders #androiddeveloper #appdeveloper #iosdeveloper #angular #vuejs #codingbootcamp #programminglife #bootstrap #htmlcss #htmlcoding #pythonprogramming #webdesigner #codingdays #nodejs #worldcode #VSCode #DeveloperTools #CodingProductivity #GameDev #Unity3D #AIGaming #IndieDev #TechTrends2026 #GameDesign #SoftwareEngineering View C2PA information 7 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Ghanshyam Gadhiya 3w Report this post Hi, This is www.KeshavInfotech.com Making a game in Unity is a big dream for many, but you need a clear path to actually finish it. In 2025, game development is changing fast with new tools and AI, so staying updated is very important. 🎮🚀 Here is a quick roadmap to help you master Unity: - Learn C#: It is the heart of Unity. Focus on clean and simple code. - Unity 6 Features: Get familiar with the latest rendering and performance tools for better graphics. - AI Tools: Use AI-powered workflows to speed up your work and automate boring tasks. - Multiplayer & Cross-Platform: More players want to play together on mobile and PC, so learn networking early. Continuous practice is what makes a great game developer. 🔑 What kind of game are you dreaming of building? Let’s chat in the comments! #JavaScriptShorthand #Mastery 🔥 #html #css #javascript #100daysofcode #webdevelopment #programming #innovation #management #digitalmarketing #technology #creativity #futurism #startups #marketing #socialmedia #socialnetworking #motivation #personaldevelopment #jobinterviews #sustainability #personalbranding #frontend #backend #developer #coding #webdeveloper #webdesign #frontenddeveloper #code #programmer #coder #webdev #web #python #java #php #codinglife #reactjs #softwaredeveloper #development #js #fullstack #software #dev #developers #ui #linkedin #instagram #facebook #twitter #business #youtube #socialmediamarketing #linkedinprofile #google #linkedintips #linkedinmarketing #jobsearch #pinterest #seo #resume #entrepreneur #career #cv #networking #branding #tiktok #linkedinlife #jobs #backenddeveloper #fullstackdeveloper #javascriptdeveloper #daysofcode #webdevelopers #developerlife #peoplewhocode #devlife #learntocode #computerscience #frontenddev #coderlife #programmers #programmerlife #codingisfun #softwareengineer #programmerslife #frontenddevelopment #coders #androiddeveloper #appdeveloper #iosdeveloper #angular #vuejs #codingbootcamp #programminglife #bootstrap #htmlcss #htmlcoding #pythonprogramming #webdesigner #codingdays #worldcode #VSCode #DeveloperTools #CodingProductivity #Unity6 #GameDev2025 #Unity3D #IndieDev #MobileGaming #GameDesign #TechInnovation View C2PA information 37 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Ekram Belal 1w Report this post 📌 QA to Game Developer Transition Plan | Step-by-Step Roadmap (2026 Ready) Want to move from QA tester to game developer but don’t know where to start? This video breaks down a clear, practical QA → Developer transition plan that shows how to go from testing games to building and shipping them. If you’re working in game QA, software testing, or manual testing, this roadmap will help you: Learn game programming the right way Build a job-ready game development portfolio Transition into Junior Game Developer / Gameplay Programmer roles Use QA skills as a competitive advantage, not a limitation 🎮 What You’ll Learn in This Video: ✔ How QA skills map directly to game development ✔ Unity vs Unreal Engine – which to choose ✔ Programming skills every game developer must learn ✔ How to become a technical QA / QA-Dev hybrid ✔ Portfolio roadmap for junior game developers ✔ How to apply for developer roles from QA 🛠 Tools & Skills Covered: Unity (C#) / Unreal Engine (C++ & Blueprints) Game programming fundamentals Bug fixing, debugging, and automation Git & GitHub for developers Test automation for games Indie & studio job strategies 👨💻 Who This Video Is For: Game QA testers Software testers wanting to become developers Beginner game developers Career switchers into game development Anyone stuck in QA and aiming for game programming jobs …more QA Skills to Game Developer | Complete Roadmap #ai #videogames #gaming https://www.youtube.com/ 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Harshit Bhatt 3w Report this post 🔧 How n8n Can Be a Game-Changer for Unity3D Projects Unity handles gameplay beautifully — but modern games and apps need automation, backend workflows, and integrations beyond the engine. That’s where n8n fits perfectly. 💡 What is n8n? n8n is an open-source workflow automation tool that connects APIs, databases, webhooks, and services — without heavy backend coding. 🚀 How n8n Helps Unity Developers 🔗 Backend Automation Without Heavy Servers - Trigger workflows from Unity using webhooks: - Player events - Match results - Analytics pings - Live ops triggers 📊 Game Analytics & Event Tracking Send gameplay data → n8n → Google Sheets / BigQuery / Slack / Email Perfect for: - Player progression tracking - Economy balancing - QA insights 🎁 Live Ops & Rewards Automation - Automate: - Daily rewards - Tournament payouts - Event unlocks - Referral rewards - All controlled outside the game build. 🔐 Auth, CRM & Tool Integrations - Connect Unity with: - Firebase - Supabase - Discord - Notion - Jira - Payment gateways Without writing complex backend glue code. 🧪 QA, Build & DevOps Triggers Trigger automated actions when: - A new build is uploaded - A test session starts - A critical error is reported ⚡ Why Unity Teams Like n8n ✔ Open-source & self-hosted ✔ No vendor lock-in ✔ Visual workflows ✔ Easy webhook support ✔ Scales from indie to enterprise 🎮 In short: Unity builds the experience. n8n automates everything around it. If you’re building multiplayer games, live-ops systems, or scalable Unity apps — n8n can save weeks of backend effort. Have you tried using automation with Unity yet? #Unity3D #GameDev #Automation #n8n #Backend #LiveOps #IndieDev #Multiplayer #GameDevelopment #ARVR #VR #indieGames View C2PA information 14 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Juan Antonio Munoz 3w Report this post Most game developers don’t fail because they lack talent. They fail because they follow a path that keeps them invisible. https://lnkd.in/gCiTiSmi I recently ran a real experiment and applied the scientific method to game development careers. Same industry, same tools, same engines, but radically different results. Some people stay stuck for years, while others build momentum, opportunities, and real careers. In this video, I break down my observations, the questions that emerged, and the patterns I discovered by studying real game dev journeys, including my own and those of successful indie developers. 🎥 Watch the full breakdown here: https://lnkd.in/gCiTiSmi If you’re learning Unreal Engine, Unity, or trying to break into the gaming industry, this will challenge how you think about progress and visibility. Thank you for watching. #gamedev #gamedevelopment #indiedev #unrealengine5 #unrealengine #unity #gameindustry #gamedevcareer #gamejobs #gameportfolio #devlog #sologamedev #careerchange #gamecreatoraccelerator 11 6 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Codekerdos 793 followers 1mo Report this post 🎮 How Multiplayer Games Match Players Using Priority Queues + Graph Ranking If you’ve ever played PUBG, Valorant, or Call of Duty… Have you noticed how matchmaking takes just a few seconds — even with millions of players online? That’s not magic. That’s DSA in action ✨ Let’s break down how real-time multiplayer games match players using Priority Queues + Graph Ranking 👇 🔥 1. Every Player Is a Node in a Graph Games treat every player as a node with attributes like: Skill rating / ELO Latency Region Win/Loss streak Behavior score Team role (support/tank/attacker) Edges connect players who are “compatible” — similar skill or available in the same mode. This forms a dynamic skill graph. 🧮 2. Ranking Players in Graph Format The game builds a ranking graph: Players near your skill level become closer nodes Players too strong/weak become far nodes Toxic players get pushed lower Friends/squad members form clusters This graph helps find the “best fit players” quickly — not randomly. ⚙️ 3. Matching Using a Priority Queue Once you hit “Start Match”, the system inserts your profile into a priority queue. Priority = 🎯 Similar skill 📡 Low ping ⏰ Waiting time 👥 Team balance 🧩 Player role The queue continuously pulls the highest priority combination of players to form a balanced match. Essentially: Build a set → Sort by priority → Pick best players → Build match. In DSA terms: Heap + Graph search = Fast, efficient matchmaking. 🚀 4. Why Priority Queues? Because heaps make insertion & extraction blazing fast: Insert → O(log n) Extract highest priority → O(log n) Even with millions of players, the matchmaking search is smooth. 🧠 5. Why Graph Ranking? Because it ensures: ✔ Fair fights ✔ Balanced teams ✔ Low ping ✔ Better gaming experience Games don’t want you getting destroyed by someone 10x stronger — the graph prevents that. 🎯 Takeaway Next time you get matched in 3–5 seconds… Remember — it’s not luck. It’s Priority Queues + Graph Ranking working behind the scenes 🔥 That’s the power of DSA in real systems. #dsa #datastructures #algorithms #coding #programming #softwareengineering #techcommunity #leetcode #geeksforgeeks #javascript #reactjs #mernstack #problemsolving #computerscience #systemdesign #developercommunity #learninginpublic #techskills #fullstackdeveloper #100daysofcode 5 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Game Design Skills 15,759 followers 1mo Report this post Studios won't hire completely fresh junior gameplay designers. Here's how you can get in: While many designers want to start out as Gameplay Designers, creating full characters (Mario) most junior jobs are about crafting small pieces (Fireballs). So, being able to demonstrate they can execute to quality on a small piece matters more than if they can plan out a full character for that first position. Most start as mechanics designers. Then level up to oversee more: enemies, environments, and much later player skills. No studio will entrust bigger responsibilities to an entry-level designer. That's why breaking into this role feels impossible. It doesn't match the reality of their training and studio expectations. Here's what we recommend: 1. Learn about game design - and understand what you want to do. Learn first the different types of designers. 2. Learn about how and where games break. Try early access titles - or if you're in a city with game studios, try a QA role to learn more and gain insights on how to become a better designer. 3. Progress on your own to junior content design, where you work on smaller gameplay pieces for about 5 years. 4. Learn game systems - they are the powerful mechanisms that most players overlook and mastering them will help you better understand player expectations. 5. Once you master all the interconnected pieces (abilities, how environments drive character design, systems, etc), and have mentors guide you while on larger projects, you're qualified for the gameplay designer role. Join our bootcamps, we’ll help you directly build your skills, portfolio, and design tests from the ground up! 👉 https://lnkd.in/e7qGwiSA 73 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Mian Hassan Sohail 3w Report this post We need to recalibrate what “SENIOR GAME DEVELOPER” really means. Across today’s game dev job market, I’m noticing a growing mismatch between titles, experience, and compensation. A quick reality check: • Most “Senior Game Developer / Senior Unity Developer” roles ask for 2-4 years of experience. • Globally, that range is typically considered junior to mid-level. • Yet these roles carry senior expectations:ownership, performance and delivery pressure. At the same time DEVELOPERS with : • 7–10+ years of experience • Multiple shipped titles • Live-ops, scalability, optimization, team leadership experience often find very few roles designed for them, and salary brackets that barely move beyond entry level ranges. This creates two problems: 1️⃣ Juniors are pressured into “senior” responsibilities too early. 2️⃣ True seniors are undervalued, underutilized, or pushed to leave the local market. And this isn’t about entitlement,it’s about sustainability. Experienced developers bring: ✅ Faster problem-solving (because they’ve already seen the failures). ✅ Better technical decisions that save months of rework. ✅ Mentorship that grows entire teams, not just individuals. ✅ Stability in production, especially under deadlines. When experience is priced too low, the industry quietly pays for it later in bugs, burnout, delays, and churn. #seniorgamedeveloper #unity3D #hiring #linkedin #gamingindustry #jobs #experience #realitycheck 40 12 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Alexander Brazie 3w Report this post You don't need a degree to be a game designer. But you do need a portfolio. Here's a fact: You can get hired with a portfolio and no degree. But you definitely won't get hired with a degree and no portfolio. I've been hiring game designers for years. When I review resumes, I only look at them to see if your portfolio is worth reviewing. Here are 8 steps to break into game design: 1. Play games critically Don't just play. Analyze. Observe how games are put together. Build a library of patterns for how developers implement design principles. At Riot, we had a Play Fund: $25/month per employee to study games through play. My mentor Tom Cadwell prescribed 20-25 hours per week of game analysis when I started. 2. Familiarize yourself with a game engine Pick Unity, Godot, Unreal, or RPG Maker. Learn the basics. Turn ideas into playable prototypes. I started using Graal Online's editor when I was 13. It helped me get some of ideas out and see how players react. It helped me get my first design role. 3. Get hands-on experience - Join game jams - Mod existing games - Build prototypes with friends - Make board/card games (no coding required) Working on mods, indie projects, and game jams shows you have drive. That's as important as talent. I modded the COSMOS UI for World of Warcraft, and it got downloaded over 1 million times. It helped me during my interview with Blizzard demonstrate that I could already solve player issues and challenges. 4. Develop a design framework Skilled designers operate using a universal process. Unskilled designers depend on intuition and the same solutions to every problem. A framework lets you identify root problems from feedback, provide practical solutions, and communicate issues effectively to your team. 5. Find a mentor Someone experienced can give you guidance can drastically shorten your learning curve. I was lost until Tom Cadwell started guiding me. His guidance got me hired at Blizzard. 6. Build your portfolio Include only your best work. Focus on pieces that show your unique talents. When you start as a junior designer, the worst mistake you can make is not asking questions and assuming you know what to do. They don't expect you to know everything. 7. Network strategically Go to game dev meetups. Join online communities like IGDA or the Funsmith Club. Meet lots of different developers. Learn about their lives, struggles, and interests. Don't just glue onto one specific person with your dream job. 8. Focus on quality over credentials Degrees are nice to have, but your portfolio is what gets you hired. When I'm hiring junior designers, it's a red flag if the applicant has a degree without meaningful projects to showcase. The main function of a game design degree? Putting it on your resume. The bottom line: Game design is a craft. Anyone who makes a game is a game designer. Landing the job is the challenge. What's stopping you from starting today? 210 24 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in 19,129 followers View Profile Connect Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://dev.to/t/machinelearning#main-content | Machine Learning - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Machine Learning Follow Hide A branch of artificial intelligence (AI) and computer science which focuses on the use of data and algorithms to imitate the way that humans learn, gradually improving its accuracy. Create Post submission guidelines Articles and discussions should be directly related to the machine learning. Questions are encouraged! (See the #help tag) Older #machinelearning posts 1 2 3 4 5 6 7 8 9 … 75 … 596 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu How to Build a Voice AI Agent for HVAC Customer Support: My Experience CallStack Tech CallStack Tech CallStack Tech Follow Jan 13 How to Build a Voice AI Agent for HVAC Customer Support: My Experience # ai # voicetech # machinelearning # webdev Comments Add Comment 14 min read Building a "Remembering" AI Trading Agent with Python, LangGraph, and Obsidian Jaeil Woo Jaeil Woo Jaeil Woo Follow Jan 11 Building a "Remembering" AI Trading Agent with Python, LangGraph, and Obsidian # opensource # python # machinelearning # ai Comments Add Comment 2 min read AI Engineering: Why the Environment Is the Most Ignored Long-Term Asset yuer yuer yuer Follow Jan 13 AI Engineering: Why the Environment Is the Most Ignored Long-Term Asset # cuda # gpu # machinelearning Comments Add Comment 5 min read Data Poisoning as Mythic Corruption: How Attackers Taint the Well of AI Narnaiezzsshaa Truong Narnaiezzsshaa Truong Narnaiezzsshaa Truong Follow Jan 12 Data Poisoning as Mythic Corruption: How Attackers Taint the Well of AI # security # programming # ai # machinelearning Comments Add Comment 6 min read perceptron - day 01 of dl Mahraib Fatima Mahraib Fatima Mahraib Fatima Follow Jan 12 perceptron - day 01 of dl # ai # beginners # deeplearning # machinelearning 1 reaction Comments Add Comment 2 min read dots-ocr: Open-Source OCR Outperforms Giants for Multilingual Automation Dr Hernani Costa Dr Hernani Costa Dr Hernani Costa Follow Jan 12 dots-ocr: Open-Source OCR Outperforms Giants for Multilingual Automation # ai # automation # machinelearning # productivity Comments Add Comment 4 min read Building GeoAI Models: From Spatial Data to Actionable Insights Koushik Vishal Annamalai Koushik Vishal Annamalai Koushik Vishal Annamalai Follow Jan 12 Building GeoAI Models: From Spatial Data to Actionable Insights # ai # machinelearning # python # gis Comments Add Comment 5 min read How to Transcribe and Detect Intent Using Deepgram for STT: A Developer's Journey CallStack Tech CallStack Tech CallStack Tech Follow Jan 12 How to Transcribe and Detect Intent Using Deepgram for STT: A Developer's Journey # ai # voicetech # machinelearning # webdev 1 reaction Comments Add Comment 11 min read The Limitations of Text Embeddings in RAG Applications: A Deep Engineering Dive Kumar Kislay Kumar Kislay Kumar Kislay Follow Jan 12 The Limitations of Text Embeddings in RAG Applications: A Deep Engineering Dive # productivity # sre # rag # machinelearning Comments Add Comment 19 min read The Essential Guide to Building a Climate Data Analysis Project Adnan Arif Adnan Arif Adnan Arif Follow Jan 12 The Essential Guide to Building a Climate Data Analysis Project # climatedata # dataanalysis # climatechange # machinelearning Comments Add Comment 8 min read Building AI Agents in 2025: From ChatGPT to Multi-Agent Systems Muhammad Zulqarnain Akram Muhammad Zulqarnain Akram Muhammad Zulqarnain Akram Follow Jan 12 Building AI Agents in 2025: From ChatGPT to Multi-Agent Systems # ai # machinelearning # python # webdev Comments Add Comment 4 min read CLI agents make self-hosting on a home server easier and fun Aman Shekhar Aman Shekhar Aman Shekhar Follow Jan 12 CLI agents make self-hosting on a home server easier and fun # ai # machinelearning # techtrends Comments Add Comment 5 min read Beyond Linear Regression: Building Proactive Risk Models with Python Rohan Shahane Rohan Shahane Rohan Shahane Follow Jan 12 Beyond Linear Regression: Building Proactive Risk Models with Python # python # datascience # machinelearning # fintech Comments Add Comment 3 min read Under the Hood: VaidhLlama Architecture & Training Pipeline Vivek Patel Vivek Patel Vivek Patel Follow Jan 12 Under the Hood: VaidhLlama Architecture & Training Pipeline # ai # machinelearning # python # finetuning 6 reactions Comments Add Comment 6 min read Cuando le dices a tu LLM "No pulses ese botón" Joaquin Jose del Cerro Murciano Joaquin Jose del Cerro Murciano Joaquin Jose del Cerro Murciano Follow Jan 12 Cuando le dices a tu LLM "No pulses ese botón" # spanish # ai # promptengineering # machinelearning Comments Add Comment 12 min read K-Means Clustering Step by Step: Beginner-Friendly Bangla Guide Moriam Akter Swarna Moriam Akter Swarna Moriam Akter Swarna Follow Jan 12 K-Means Clustering Step by Step: Beginner-Friendly Bangla Guide # machinelearning # clustering # kmeansclustering Comments Add Comment 3 min read 3 Ways to Run AI in the Browser with Next.js (No API Keys Required) Niroshan Dh Niroshan Dh Niroshan Dh Follow Jan 12 3 Ways to Run AI in the Browser with Next.js (No API Keys Required) # javascript # webdev # ai # machinelearning Comments Add Comment 3 min read AWS Certified Generative AI Developer – Professional in 2 Weeks (Part 1: Exam Overview & Foundations) MakendranG MakendranG MakendranG Follow Jan 11 AWS Certified Generative AI Developer – Professional in 2 Weeks (Part 1: Exam Overview & Foundations) # ai # machinelearning # aws # certification 6 reactions Comments Add Comment 16 min read AWS Certified Generative AI Developer – Professional: Exam Overview & Foundation Strategy (Part 1) MakendranG MakendranG MakendranG Follow Jan 11 AWS Certified Generative AI Developer – Professional: Exam Overview & Foundation Strategy (Part 1) # ai # machinelearning # aws # certification 6 reactions Comments Add Comment 7 min read How to Build Custom Pipelines for Voice AI Integration: A Developer's Journey CallStack Tech CallStack Tech CallStack Tech Follow Jan 11 How to Build Custom Pipelines for Voice AI Integration: A Developer's Journey # ai # voicetech # machinelearning # webdev 1 reaction Comments Add Comment 13 min read From Manual Testing to AI Pipelines: Lessons That Never Changed in My QA Career Adnan Arif Adnan Arif Adnan Arif Follow Jan 12 From Manual Testing to AI Pipelines: Lessons That Never Changed in My QA Career # ai # machinelearning # testing Comments Add Comment 4 min read Paper Review: Scaling Up to Excellence: Practicing Model Scaling for Photo-Realistic Image Restoration In the Wild Evan Lin Evan Lin Evan Lin Follow Jan 11 Paper Review: Scaling Up to Excellence: Practicing Model Scaling for Photo-Realistic Image Restoration In the Wild # computerscience # machinelearning # deeplearning # ai Comments Add Comment 2 min read Production ML is not about models. It’s about trade-offs. Jashwanth Thatipamula Jashwanth Thatipamula Jashwanth Thatipamula Follow Jan 11 Production ML is not about models. It’s about trade-offs. # webdev # ai # machinelearning # programming 3 reactions Comments Add Comment 3 min read The Non-Drinker's Guide to Clustering Algorithms 🎉 Seenivasa Ramadurai Seenivasa Ramadurai Seenivasa Ramadurai Follow Jan 11 The Non-Drinker's Guide to Clustering Algorithms 🎉 # algorithms # beginners # datascience # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #134: RAG Architecture Misunderstanding - Wrong Fix Applied Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #134: RAG Architecture Misunderstanding - Wrong Fix Applied # ai # trading # python # machinelearning Comments Add Comment 2 min read loading... trending guides/resources Beyond Coding: Your Accountability Buddy with Claude Code Skill If You’re Learning AI, These 5 Books Are All You Need AI World Clocks Qwen-Image-Edit-2511：人物一致性再上新台阶 LightRAG Tutorial: A Practical Guide to Knowledge Graph-Based RAG Train a Custom Z‑Image Turbo LoRA with the Ostris AI Toolkit (RunPod Edition) Complete Guide to Run AI Models Locally, Even on Mid-Tier Laptop Prompt Length vs. Context Window: The Real Limits Behind LLM Performance Building a Unified Benchmarking Pipeline for Computer Vision — Without Rewriting Code for Every Task A step-by-step guide to fine-tuning MedGemma for breast tumor classification Fabrice Bellard Releases MicroQuickJS Building Sentence Transformers in Rust: A Practical Guide with Burn, ONNX Runtime, and Candle 5 Key Performance Benchmarks for AI Development in 2025 LightRAG Tutorial: Getting Started with Knowledge Graph-Based RAG Z-Image: Alibaba's 6B-Parameter Open-Source Model Revolutionizes Efficient Image Generation Amazing Z-Image Workflow v3.0: Complete Guide to Enhanced ComfyUI Image Generation Toon: A Lightweight Data Format That Helps Cut LLM Token Costs ESP32-S3 + TensorFlow Lite Micro: A Practical Guide to Local Wake Word & Edge AI Inference Join the AI Agents Intensive Course Writing Challenge with Google and Kaggle Cracking the Medical Coding Challenge: Fine-Tuning BioBERT for ICD-10 Classification (Part 1) 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/ios-push-template#content-area | iOS Push Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors iOS Push Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors iOS Push Template OpenAI Open in ChatGPT How to design simple iOS Push template with click action and image. OpenAI Open in ChatGPT Design Template You can design template with a simple form editor tool. You can add variables with Handlebarsjs language. You can check how the message will look in the preview section on the right side. Once designed, you can save the push notification template by clicking on Save Draft. When you are ready, you can Publish Draft by providing a name to the version. This will become the Live version, and will be used whenever the associated workflow is triggered. iOS Push notification fields description Field Description Title Small message text box. Note that this field will be displayed in single line only, and very long content can get curtailed. Use handlebarsjs to add variables. Body Large message text box. Use handlebarsjs to add variables. 📘 Note: By default, Clicking on the Notification will redirect the users to your iOS App. We’ll be soon be adding the option to add custom Action URL Adding dynamic content in iOS Push There will always be the case where you would require to add dynamic content to a template, so as to personalise it for your users. To achieve this, you can add variables in the template, which will be replaced with the dynamic content at the time of sending the message. You’ll need to pass these while triggering the communication from one of our frontend or backend SDKs. Here is a step-by-step guide on how to add dynamic content in iOS Push: 1 Declaring Variables in the global `Mock data` button If you are at this stage, it is assumed that you have declared the variables along with sample values in the global Mock data button. To see how to declare variables before using them in designing templates, refer to this section in the Templates documentation . 2 Using variables in the templates Once the variables are declared, you can use them while designing the iOS Push template. We support handlebarsjs to add variables in the template. As a general rule, all the variables have to be entered within double curly brackets: {{variable\_name}} If you have declared the variables in the global Mock data button, then they will come as auto-suggestions when you type a curly bracket { . This will remove the chances of errors like variable mismatch at the time of template rendering. Note that you will be able to enter a variable name even when you have not declared it inside the Mock data button. To manually enter the variable name, follow the handlerbarsjs guide here . Below is an example of how to enter variables in the template design. For illustration, we are using the same sample variable names that we declared in the Templates section: json Copy Ask AI { "array" : [ { "product_name" : "Aldo Sling Bag" , "product_price" : "3,950.00" }, { "product_name" : "Clarles & Keith Women Slipper, Biege, 38UK" , "product_price" : "2,549.00" }, { "product_name" : "RayBan Sunglasses" , "product_price" : "7,899.00" } ], "event" : { "location" : { "city" : "San Francisco" , "state" : "California" }, "order_id" : "11200123" , "first_name" : "Joe" }, "product_page" : "https://www.suprsend.com" } To enter a nested variable, enter in the format {{var1.var2.var3}} . E.g. to refer to city in the example above, you need to enter {{event.location.city}} To refer to an array element, enter in format {{var1.[*index*].var2}}. E.g. to refer to product_name of the first element of the array array , enter {{array.[0].product_name}}` If you have any space in the variable name, enclose it in square bracket {{event.[first name]}} You will be able to see the sample values in the Preview section, as well as in the Live version when you publish a draft. If you cannot see your variable being rendered with the sample value, check one of the following: Make sure you have entered the variable name and the sample value in the Mock data button. Make sure you have entered the correct variable name in the template, as per the handlebarsjs guideline. What happens if there is variable mismatch at the time of sending? At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user. Please note that the rest of the templates will be sent. E.g. if there is an error in rendering iOS Push template, but email template is successfully rendered, iOS Push notification will not be triggered, but email notification will be triggered by SuprSend. Was this page helpful? Yes No Suggest edits Raise issue Previous Web Push Template How to design Webpush template with customisation options to add action buttons and image. Next ⌘ I x github linkedin youtube Powered by On this page Design Template iOS Push notification fields description Adding dynamic content in iOS Push | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/ | MDN Web Docs Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog MDN Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Resources for Developers, by Developers Documenting CSS , HTML , and JavaScript , since 2005. Search Mandala / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + { { { { } } } } { { { { } } } } { { { { } } } } { { { { } } } } { { { { } } } } { { { { } } } } ../../ ../../ ../../ ../../ ../../ ../../ ../../ <> </> <> </> <> </> <> </> <> </> <> </> <> </> <> </> <> </> <> </> <> </> <> </> <> </> <> </> <> </> <> </> Featured articles Blog Celebrating 20 years of MDN MDN turns 20! Let's look at how we started, how MDN became the most trusted resource for web developers, the impact it's had on the open web, and yes, there's cake, too. Web APIs CSS Custom Highlight API The CSS Custom Highlight API provides a mechanism for styling arbitrary text ranges on a document by using JavaScript to create the ranges, and CSS to style them. Web APIs Server timing Server-Timing is a part of the Performance API and allows servers to communicate metrics about the request-response cycle to the user agent. You can collect this information and act on server-side metrics in the same way as all the other metrics processed with the Performance API. JavaScript JavaScript resource management This guide talks about how to do resource management in JavaScript. Resource management is not exactly the same as memory management, which is a more advanced topic and usually handled automatically by JavaScript. Resource management is about managing resources that are not automatically cleaned up by JavaScript. Sometimes, it's okay to have some unused objects in memory, because they don't interfere with application logic, but resource leaks often lead to things not working, or a lot of excess memory usage. Therefore, this is not an optional feature about optimization, but a core feature to write correct programs! Latest news developer.mozilla.org Launching MDN's new front end 5 months ago MDN is getting a facelift 🎉. Discover what's changed, what's improved, and how navigating the site just got smoother. developer.mozilla.org Image formats: Pixel data from encoders to decoders 5 months ago From individual pixels to fully decoded images on your screen, raw pixel data gets transformed, compressed, and efficiently delivered. Learn about the techniques and optimizations that shrink image information without any perceivable loss in quality. developer.mozilla.org Image formats: Color models for humans and devices 8 months ago Images help bring more color and life to the web. This post describes how images are represented by humans and on different devices, with details about color spaces and vision theory. developer.mozilla.org Default styles for h1 elements are changing 9 months ago Browsers are starting to roll out changes in default UA styles for nested section headings. This post describes the incoming changes, how to identify if it's an issue on your websites, and hints for conformant and better-structured pages. Recent contributions mdn/translated-content 1 day ago [ru] fix http methods mistakes mdn/translated-content 11 hours ago chore(deps-dev): bump lefthook from 2.0.13 to 2.0.14 mdn/content 7 hours ago Fix typo in `using_deferred_fetch` mdn/content 7 hours ago chore(deps-dev): bump lefthook from 2.0.13 to 2.0.14 mdn/content 7 hours ago chore(deps-dev): bump cspell from 9.4.0 to 9.6.0 mdn/content 5 hours ago Fix incorrect inheritance description for Range interface mdn/content 5 hours ago Fix typo in intersection_observer_api Contributor Spotlight Shrinivass Arunachalam Balasubramanian MDN closely follows W3C standards which helps me keep up with important topics. It's a complete package as it caters to everything; complex APIs, new browser functionalities, and best practices. MDN serves as a truly valuable resource and continues to assist me in my everyday development. Get involved Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://www.youtube.com/watch?v=-jpLqtAWKfo | Two brothers build Shazam for food | Introducing Nutrify - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0xa6c640dec8f6c807"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtzUV9VaVBRWlFCMCjWjZjLBjIKCgJLUhIEGgAgUA%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZR7CFZsBOAo-cWoLaB0By_k6MgIxiOEv8uoiHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","metadataBadgeRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","chapterRenderer","notificationActionRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","macroMarkersListRenderer","macroMarkersListItemRenderer","toggleButtonRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","expandableMetadataRenderer","videoSummaryContentViewModel","videoSummaryParagraphViewModel","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer","microformatDataRenderer"]},"ytConfigData":{"visitorData":"CgtzUV9VaVBRWlFCMCjWjZjLBjIKCgJLUhIEGgAgUA%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwjPgffukIiSAxV6djgFHZg5LZgyDHJlbGF0ZWQtYXV0b0j609iArfWSnfoBmgEFCAMQ-B3KAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pZXt-flSAZo\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pZXt-flSAZo","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjPgffukIiSAxV6djgFHZg5LZgyDHJlbGF0ZWQtYXV0b0j609iArfWSnfoBmgEFCAMQ-B3KAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pZXt-flSAZo\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pZXt-flSAZo","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjPgffukIiSAxV6djgFHZg5LZgyDHJlbGF0ZWQtYXV0b0j609iArfWSnfoBmgEFCAMQ-B3KAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pZXt-flSAZo\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pZXt-flSAZo","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"Two brothers build Shazam for food | Introducing Nutrify"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 13,352회"},"shortViewCount":{"simpleText":"조회수 1.3만회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CNoCEMyrARgAIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESCy1qcExxdEFXS2ZvGmBFZ3N0YW5CTWNYUkJWMHRtYjBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTHkxcWNFeHhkRUZYUzJadkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CNoCEMyrARgAIhMIz4H37pCIkgMVenY4BR2YOS2Y"}}],"trackingParams":"CNoCEMyrARgAIhMIz4H37pCIkgMVenY4BR2YOS2Y","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"641","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COgCEKVBIhMIz4H37pCIkgMVenY4BR2YOS2Y"}},{"innertubeCommand":{"clickTrackingParams":"COgCEKVBIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"COkCEPqGBCITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COkCEPqGBCITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"-jpLqtAWKfo"},"likeParams":"Cg0KCy1qcExxdEFXS2ZvIAAyDAjXjZjLBhDOq4rvAQ%3D%3D"}},"idamTag":"66426"}},"trackingParams":"COkCEPqGBCITCM-B9-6QiJIDFXp2OAUdmDktmA=="}}}}}}}]}},"accessibilityText":"다른 사용자 641명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COgCEKVBIhMIz4H37pCIkgMVenY4BR2YOS2Y","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"642","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COcCEKVBIhMIz4H37pCIkgMVenY4BR2YOS2Y"}},{"innertubeCommand":{"clickTrackingParams":"COcCEKVBIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"-jpLqtAWKfo"},"removeLikeParams":"Cg0KCy1qcExxdEFXS2ZvGAAqDAjXjZjLBhDgk4vvAQ%3D%3D"}}}]}},"accessibilityText":"다른 사용자 641명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COcCEKVBIhMIz4H37pCIkgMVenY4BR2YOS2Y","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CNoCEMyrARgAIhMIz4H37pCIkgMVenY4BR2YOS2Y","isTogglingDisabled":true}},"likeStatusEntityKey":"EgstanBMcXRBV0tmbyA-KAE%3D","likeStatusEntity":{"key":"EgstanBMcXRBV0tmbyA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COUCEKiPCSITCM-B9-6QiJIDFXp2OAUdmDktmA=="}},{"innertubeCommand":{"clickTrackingParams":"COUCEKiPCSITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"COYCEPmGBCITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COYCEPmGBCITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"-jpLqtAWKfo"},"dislikeParams":"Cg0KCy1qcExxdEFXS2ZvEAAiDAjXjZjLBhCytYzvAQ%3D%3D"}},"idamTag":"66425"}},"trackingParams":"COYCEPmGBCITCM-B9-6QiJIDFXp2OAUdmDktmA=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COUCEKiPCSITCM-B9-6QiJIDFXp2OAUdmDktmA==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COQCEKiPCSITCM-B9-6QiJIDFXp2OAUdmDktmA=="}},{"innertubeCommand":{"clickTrackingParams":"COQCEKiPCSITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"-jpLqtAWKfo"},"removeLikeParams":"Cg0KCy1qcExxdEFXS2ZvGAAqDAjXjZjLBhCW1IzvAQ%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COQCEKiPCSITCM-B9-6QiJIDFXp2OAUdmDktmA==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CNoCEMyrARgAIhMIz4H37pCIkgMVenY4BR2YOS2Y","isTogglingDisabled":true}},"dislikeEntityKey":"EgstanBMcXRBV0tmbyA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgstanBMcXRBV0tmbyD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COICEOWWARgHIhMIz4H37pCIkgMVenY4BR2YOS2Y"}},{"innertubeCommand":{"clickTrackingParams":"COICEOWWARgHIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgstanBMcXRBV0tmb6ABAQ%3D%3D","commands":[{"clickTrackingParams":"COICEOWWARgHIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"COMCEI5iIhMIz4H37pCIkgMVenY4BR2YOS2Y","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COICEOWWARgHIhMIz4H37pCIkgMVenY4BR2YOS2Y","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"COACEOuQCSITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"COECEPuGBCITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D-jpLqtAWKfo\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COECEPuGBCITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"-jpLqtAWKfo","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2es.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=fa3a4baad01629fa\u0026ip=1.208.108.242\u0026initcwndbps=3033750\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NA\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}},"idamTag":"66427"}},"trackingParams":"COECEPuGBCITCM-B9-6QiJIDFXp2OAUdmDktmA=="}}}}}},"trackingParams":"COACEOuQCSITCM-B9-6QiJIDFXp2OAUdmDktmA=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CN4CEOuQCSITCM-B9-6QiJIDFXp2OAUdmDktmA=="}},{"innertubeCommand":{"clickTrackingParams":"CN4CEOuQCSITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CN8CEPuGBCITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D-jpLqtAWKfo\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CN8CEPuGBCITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"-jpLqtAWKfo","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2es.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=fa3a4baad01629fa\u0026ip=1.208.108.242\u0026initcwndbps=3033750\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NA\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}},"idamTag":"66427"}},"trackingParams":"CN8CEPuGBCITCM-B9-6QiJIDFXp2OAUdmDktmA=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CN4CEOuQCSITCM-B9-6QiJIDFXp2OAUdmDktmA==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CNoCEMyrARgAIhMIz4H37pCIkgMVenY4BR2YOS2Y","superTitleLink":{"runs":[{"text":"#ai","navigationEndpoint":{"clickTrackingParams":"CN0CEKW3AxgAIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/ai","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUGCgJhaRgB"}},"loggingDirectives":{"trackingParams":"CN0CEKW3AxgAIhMIz4H37pCIkgMVenY4BR2YOS2Y","visibility":{"types":"12"}}},{"text":" "},{"text":"#nutrition","navigationEndpoint":{"clickTrackingParams":"CNwCEKW3AxgCIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/nutrition","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUNCgludXRyaXRpb24YAQ%3D%3D"}},"loggingDirectives":{"trackingParams":"CNwCEKW3AxgCIhMIz4H37pCIkgMVenY4BR2YOS2Y","visibility":{"types":"12"}}},{"text":" "},{"text":"#machinelearning","navigationEndpoint":{"clickTrackingParams":"CNsCEKW3AxgEIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/machinelearning","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUTCg9tYWNoaW5lbGVhcm5pbmcYAQ%3D%3D"}},"loggingDirectives":{"trackingParams":"CNsCEKW3AxgEIhMIz4H37pCIkgMVenY4BR2YOS2Y","visibility":{"types":"12"}}}]},"dateText":{"simpleText":"2024. 2. 11."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"1년 전"}},"simpleText":"1년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/ytc/AIdro_keYELwerQt-4bRlMYF5E2S-d6uxLBtGLObXTNgVQwimIzJ=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/ytc/AIdro_keYELwerQt-4bRlMYF5E2S-d6uxLBtGLObXTNgVQwimIzJ=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/ytc/AIdro_keYELwerQt-4bRlMYF5E2S-d6uxLBtGLObXTNgVQwimIzJ=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Daniel Bourke","navigationEndpoint":{"clickTrackingParams":"CNkCEOE5IhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"url":"/@mrdbourke","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCr8O8l5cCX85Oem1d18EezQ","canonicalBaseUrl":"/@mrdbourke"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CNkCEOE5IhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"url":"/@mrdbourke","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCr8O8l5cCX85Oem1d18EezQ","canonicalBaseUrl":"/@mrdbourke"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 24만명"}},"simpleText":"구독자 24만명"},"trackingParams":"CNkCEOE5IhMIz4H37pCIkgMVenY4BR2YOS2Y","badges":[{"metadataBadgeRenderer":{"icon":{"iconType":"CHECK_CIRCLE_THICK"},"style":"BADGE_STYLE_TYPE_VERIFIED","tooltip":"인증됨","trackingParams":"CNkCEOE5IhMIz4H37pCIkgMVenY4BR2YOS2Y","accessibilityData":{"label":"인증됨"}}}]}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCr8O8l5cCX85Oem1d18EezQ","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CMsCEJsrIhMIz4H37pCIkgMVenY4BR2YOS2YKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Daniel Bourke을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Daniel Bourke을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Daniel Bourke 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CNgCEPBbIhMIz4H37pCIkgMVenY4BR2YOS2Y","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Daniel Bourke 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Daniel Bourke 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CNcCEPBbIhMIz4H37pCIkgMVenY4BR2YOS2Y","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Daniel Bourke 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CNACEJf5ASITCM-B9-6QiJIDFXp2OAUdmDktmA==","command":{"clickTrackingParams":"CNACEJf5ASITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CNACEJf5ASITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CNYCEOy1BBgDIhMIz4H37pCIkgMVenY4BR2YOS2YMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ3I4TzhsNWNDWDg1T2VtMWQxOEVlelESAggBGAAgBFITCgIIAxILLWpwTHF0QVdLZm8YAA%3D%3D"}},"trackingParams":"CNYCEOy1BBgDIhMIz4H37pCIkgMVenY4BR2YOS2Y","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CNUCEO21BBgEIhMIz4H37pCIkgMVenY4BR2YOS2YMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ3I4TzhsNWNDWDg1T2VtMWQxOEVlelESAggDGAAgBFITCgIIAxILLWpwTHF0QVdLZm8YAA%3D%3D"}},"trackingParams":"CNUCEO21BBgEIhMIz4H37pCIkgMVenY4BR2YOS2Y","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CNECENuLChgFIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CNECENuLChgFIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CNICEMY4IhMIz4H37pCIkgMVenY4BR2YOS2Y","dialogMessages":[{"runs":[{"text":"Daniel Bourke"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CNQCEPBbIhMIz4H37pCIkgMVenY4BR2YOS2YMgV3YXRjaMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCr8O8l5cCX85Oem1d18EezQ"],"params":"CgIIAxILLWpwTHF0QVdLZm8YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CNQCEPBbIhMIz4H37pCIkgMVenY4BR2YOS2Y"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CNMCEPBbIhMIz4H37pCIkgMVenY4BR2YOS2Y"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CNECENuLChgFIhMIz4H37pCIkgMVenY4BR2YOS2Y"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CMsCEJsrIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CM8CEP2GBCITCM-B9-6QiJIDFXp2OAUdmDktmDIJc3Vic2NyaWJlygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D-jpLqtAWKfo%26continue_action%3DQUFFLUhqbjZYTFdfVDBsazF1RXhiMXZ2ZmZMd3VyWlVjUXxBQ3Jtc0tsNDdBeHd3Nkstd3ZVSnoxbjhXTGtZajlEN0JCcVpZU0V4aVdmSERLOWhjLTJaYXdqcFdHaG9ZcXpVSEpKSHRodmVXTW1FQXVBMVUtNmVwLU4tdXo1RkFCWUpaT21qbDRSeWlMUlJ3TTZBelp4OWV0VGxvTlF6MC12UzJqWUdBd3diczVTWUg2MmZQdTcwdkZpR28zaHE3VV9qVkMya2RGNHI0VFE2dy1MRDBuNlUtU1Z6LVhjeFhNYUNZcUZMZjVCTnR4TkI\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CM8CEP2GBCITCM-B9-6QiJIDFXp2OAUdmDktmMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"-jpLqtAWKfo","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2es.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=fa3a4baad01629fa\u0026ip=1.208.108.242\u0026initcwndbps=3033750\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NA\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}},"continueAction":"QUFFLUhqbjZYTFdfVDBsazF1RXhiMXZ2ZmZMd3VyWlVjUXxBQ3Jtc0tsNDdBeHd3Nkstd3ZVSnoxbjhXTGtZajlEN0JCcVpZU0V4aVdmSERLOWhjLTJaYXdqcFdHaG9ZcXpVSEpKSHRodmVXTW1FQXVBMVUtNmVwLU4tdXo1RkFCWUpaT21qbDRSeWlMUlJ3TTZBelp4OWV0VGxvTlF6MC12UzJqWUdBd3diczVTWUg2MmZQdTcwdkZpR28zaHE3VV9qVkMya2RGNHI0VFE2dy1MRDBuNlUtU1Z6LVhjeFhNYUNZcUZMZjVCTnR4TkI","idamTag":"66429"}},"trackingParams":"CM8CEP2GBCITCM-B9-6QiJIDFXp2OAUdmDktmA=="}}}}}},"subscribedEntityKey":"EhhVQ3I4TzhsNWNDWDg1T2VtMWQxOEVlelEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CMsCEJsrIhMIz4H37pCIkgMVenY4BR2YOS2YKPgdMgV3YXRjaMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCr8O8l5cCX85Oem1d18EezQ"],"params":"EgIIAxgAIgstanBMcXRBV0tmbw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CMsCEJsrIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMsCEJsrIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CMwCEMY4IhMIz4H37pCIkgMVenY4BR2YOS2Y","dialogMessages":[{"runs":[{"text":"Daniel Bourke"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CM4CEPBbIhMIz4H37pCIkgMVenY4BR2YOS2YKPgdMgV3YXRjaMoBBP_zGSU=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCr8O8l5cCX85Oem1d18EezQ"],"params":"CgIIAxILLWpwTHF0QVdLZm8YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CM4CEPBbIhMIz4H37pCIkgMVenY4BR2YOS2Y"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CM0CEPBbIhMIz4H37pCIkgMVenY4BR2YOS2Y"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2Y"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2Y","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Nutrify allows you to take a photo of food and learn about it. Consider it a Pokédex for food or Shazam for food.\n\nDownload Nutrify on the App Store - https://apple.co/4ahM7Wc\nNutrify website - https://www.nutrify.app\nNutrify Instagram - / nutrifyfoodapp \nQuestions? - support@nutrify.app\n\nOther links:\nLearn AI/ML (beginner-friendly course) - https://dbourke.link/ZTMMLcourse \nLearn TensorFlow - https://dbourke.link/ZTMTFcourse \nLearn PyTorch - https://dbourke.link/ZTMPyTorch \nAI/ML courses/books I recommend - https://www.mrdbourke.com/ml-resources/ \nRead my novel Charlie Walks - https://www.charliewalks.com \n\nConnect elsewhere:\nWeb - https://dbourke.link/web \nTwitter - / mrdbourke \nTwitch - / mrdbourke \nArXiv channel (past streams) - https://dbourke.link/archive-channel \nGet email updates on my work - https://dbourke.link/newsletter \n\nTimestamps:\n0:00 - Intro\n0:37 - How it started\n2:34 - How it's going\n3:09 - Nutrify philosophy\n4:08 - Create a visual food diary\n4:42 - Fill out the Nutridex\n6:20 - Get stats over time\n6:52 - Where it's going\n8:13 - Outro\n\n#nutrify #nutrition #machinelearning #ai","commandRuns":[{"startIndex":151,"length":24,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbEl1OXZ1YlRZdk5LSE41XzE3SjhteTlwYzU0d3xBQ3Jtc0trc3F3VWtzYWZ3RG12cTJrWUMtOFdhbGFoaGRfYTExd3V2TGdxZ1BRVXhPLWFkU2VERGpvc1VzNnIxTkRHbnpiMWlRZEZxc3NlREpOOHd0TE1rV1h0bG55aHgwd0JyWFpsZ2JJNzlCUGJ1TkZHdENvMA\u0026q=https%3A%2F%2Fapple.co%2F4ahM7Wc\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbEl1OXZ1YlRZdk5LSE41XzE3SjhteTlwYzU0d3xBQ3Jtc0trc3F3VWtzYWZ3RG12cTJrWUMtOFdhbGFoaGRfYTExd3V2TGdxZ1BRVXhPLWFkU2VERGpvc1VzNnIxTkRHbnpiMWlRZEZxc3NlREpOOHd0TE1rV1h0bG55aHgwd0JyWFpsZ2JJNzlCUGJ1TkZHdENvMA\u0026q=https%3A%2F%2Fapple.co%2F4ahM7Wc\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":194,"length":23,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbjhUVnhMdU1pM3pGaHRBdmxYNzRPVERsOGVDd3xBQ3Jtc0tsMW9hYjdoX2pjU2JkSE1QSTJSSE5IZmtNXzNJT0xHa3RJTlRBc3M2MWh4MGR3MlE4endVbkxYSW9MR3NVcjUzLVVKemZ0MFRkT1M0NzBDQ1RBZEh6VVVERjV0NkkyYUVYZ25NU1Z3a3RoMFE3SW1mdw\u0026q=https%3A%2F%2Fwww.nutrify.app%2F\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbjhUVnhMdU1pM3pGaHRBdmxYNzRPVERsOGVDd3xBQ3Jtc0tsMW9hYjdoX2pjU2JkSE1QSTJSSE5IZmtNXzNJT0xHa3RJTlRBc3M2MWh4MGR3MlE4endVbkxYSW9MR3NVcjUzLVVKemZ0MFRkT1M0NzBDQ1RBZEh6VVVERjV0NkkyYUVYZ25NU1Z3a3RoMFE3SW1mdw\u0026q=https%3A%2F%2Fwww.nutrify.app%2F\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":238,"length":20,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbVo5Vm5hTlZMaVZPelljVFVjWGtIMUJYOTFnUXxBQ3Jtc0tsOWFFbTRwaXFBd09jLTRRbnN0Nmk5YmM2QkpQZ3d6RnhqQXR1MV9zN3h1WGE3ZUFyYnZuWkU3UHB1M2hpenU1cU9xelllZzhua2lLYkhrcEZsdkRyWkFSaG1UOXJ1bzFKOEc3cXZEVGlpLWcwZkhUdw\u0026q=https%3A%2F%2Fwww.instagram.com%2Fnutrifyfoodapp\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbVo5Vm5hTlZMaVZPelljVFVjWGtIMUJYOTFnUXxBQ3Jtc0tsOWFFbTRwaXFBd09jLTRRbnN0Nmk5YmM2QkpQZ3d6RnhqQXR1MV9zN3h1WGE3ZUFyYnZuWkU3UHB1M2hpenU1cU9xelllZzhua2lLYkhrcEZsdkRyWkFSaG1UOXJ1bzFKOEc3cXZEVGlpLWcwZkhUdw\u0026q=https%3A%2F%2Fwww.instagram.com%2Fnutrifyfoodapp\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Instagram Channel Link: nutrifyfoodapp"}}},{"startIndex":347,"length":32,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0pLTHBUT19nS1BBRmhsOGpBc1NxRFROaGozZ3xBQ3Jtc0tteFdCSl93eXQtR0s0ai0zWVFHeHVONzZTSGRnOFhpekZJYnlQelpZM1MzZk04aElUR1BUM1M5RmNudy1sWlFsMk9VRUtERFBvaGlNbEVWVzczNElYOGgxNmxMY1dyVjF4N1JuX2RVR2xKQ1NxMGtzRQ\u0026q=https%3A%2F%2Fdbourke.link%2FZTMMLcourse\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0pLTHBUT19nS1BBRmhsOGpBc1NxRFROaGozZ3xBQ3Jtc0tteFdCSl93eXQtR0s0ai0zWVFHeHVONzZTSGRnOFhpekZJYnlQelpZM1MzZk04aElUR1BUM1M5RmNudy1sWlFsMk9VRUtERFBvaGlNbEVWVzczNElYOGgxNmxMY1dyVjF4N1JuX2RVR2xKQ1NxMGtzRQ\u0026q=https%3A%2F%2Fdbourke.link%2FZTMMLcourse\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":400,"length":32,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0doaVZJT3J6Vm5COWVTV1pKUEdiV0FNaHpMZ3xBQ3Jtc0tsb3RmOTBSajRuYkk0bHhEaFFtR2w3SkNrSHhTWjlHLXpidGN4SXFKajdybmVvSjJOVnMzdl9uVy13aXJ4c1pKMk9nc1BOTXFMRmY1R0hNUmc5aC1WOE4za0xudV85Y0FNZDg1eGw5YjU3X05aWWlGcw\u0026q=https%3A%2F%2Fdbourke.link%2FZTMTFcourse\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0doaVZJT3J6Vm5COWVTV1pKUEdiV0FNaHpMZ3xBQ3Jtc0tsb3RmOTBSajRuYkk0bHhEaFFtR2w3SkNrSHhTWjlHLXpidGN4SXFKajdybmVvSjJOVnMzdl9uVy13aXJ4c1pKMk9nc1BOTXFMRmY1R0hNUmc5aC1WOE4za0xudV85Y0FNZDg1eGw5YjU3X05aWWlGcw\u0026q=https%3A%2F%2Fdbourke.link%2FZTMTFcourse\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":450,"length":31,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa2Vrd2ZIRWt6UmFOTDFEaWhuSDFGanJZRVBOUXxBQ3Jtc0tuWWJ3bnEydXhKSEJhanV5LWJKNGM4MXJwc2lubk1mUVVqV2tzek93TEZtTFQ3TXlOR044QVVSbERkaThEYjh5LUQ3Z3YwRS02em9WS2xBT1lUbExPZUk1VzhxTkZkRThQU0VqaTl4bGhkWHVKUU5VUQ\u0026q=https%3A%2F%2Fdbourke.link%2FZTMPyTorch\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa2Vrd2ZIRWt6UmFOTDFEaWhuSDFGanJZRVBOUXxBQ3Jtc0tuWWJ3bnEydXhKSEJhanV5LWJKNGM4MXJwc2lubk1mUVVqV2tzek93TEZtTFQ3TXlOR044QVVSbERkaThEYjh5LUQ3Z3YwRS02em9WS2xBT1lUbExPZUk1VzhxTkZkRThQU0VqaTl4bGhkWHVKUU5VUQ\u0026q=https%3A%2F%2Fdbourke.link%2FZTMPyTorch\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":517,"length":39,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbDQ3Vmk2aHJab2VqbXY5eWdhZUNmUGlqQTJEQXxBQ3Jtc0trRWhlMXI1ZkFCR2hmUDNZSjNyNFNkcHg4ckpPU2FMNDJVN3BIc01yc1NhVWxReDNBUm85eFZOa3pBTXhZQ2pQS3dSTUloWExHS3Q5SFFpOWJFWlhjdlRVOWlVd21OMF9ZNUUzMHlMaWJFREh6YTdWVQ\u0026q=https%3A%2F%2Fwww.mrdbourke.com%2Fml-resources%2F\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbDQ3Vmk2aHJab2VqbXY5eWdhZUNmUGlqQTJEQXxBQ3Jtc0trRWhlMXI1ZkFCR2hmUDNZSjNyNFNkcHg4ckpPU2FMNDJVN3BIc01yc1NhVWxReDNBUm85eFZOa3pBTXhZQ2pQS3dSTUloWExHS3Q5SFFpOWJFWlhjdlRVOWlVd21OMF9ZNUUzMHlMaWJFREh6YTdWVQ\u0026q=https%3A%2F%2Fwww.mrdbourke.com%2Fml-resources%2F\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":588,"length":28,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbFVlR3VQdFpHUzM3cjBJeER3cWE2R1I5UXkzQXxBQ3Jtc0trVi1QWFZGMkVfRXpqMGpkZzAzLWJPbUp0VzBhaExHd2NxTE9fbWpXV0wwU0RZRHN1TGwtRzBaM0o4VjhtQkZvOC0wZ0R3WmdtSlN6YV9UUGliRTF2Mkc3bXF0OXpMZzE2OTBCbktWS3Flajdxd3l3SQ\u0026q=https%3A%2F%2Fwww.charliewalks.com%2F\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbFVlR3VQdFpHUzM3cjBJeER3cWE2R1I5UXkzQXxBQ3Jtc0trVi1QWFZGMkVfRXpqMGpkZzAzLWJPbUp0VzBhaExHd2NxTE9fbWpXV0wwU0RZRHN1TGwtRzBaM0o4VjhtQkZvOC0wZ0R3WmdtSlN6YV9UUGliRTF2Mkc3bXF0OXpMZzE2OTBCbktWS3Flajdxd3l3SQ\u0026q=https%3A%2F%2Fwww.charliewalks.com%2F\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":644,"length":24,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbTBGdWNrZlc0czVVUGlEMEplcHFUQ1otR0szZ3xBQ3Jtc0tsc1dxRjl6MXFzeEdFS2oyTjhaS0t0d0V0Ynl1dEpHVzRWZ3NFUEg1N19YbWZlekl5UFBDeFlfbDZGb05scERjWmxZRGt3MmJzVTlNWnZ1STZBQXhtMUVQMjNkUUt4VjE5U01qODU0TzFTN2RYUWN6dw\u0026q=https%3A%2F%2Fdbourke.link%2Fweb\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbTBGdWNrZlc0czVVUGlEMEplcHFUQ1otR0szZ3xBQ3Jtc0tsc1dxRjl6MXFzeEdFS2oyTjhaS0t0d0V0Ynl1dEpHVzRWZ3NFUEg1N19YbWZlekl5UFBDeFlfbDZGb05scERjWmxZRGt3MmJzVTlNWnZ1STZBQXhtMUVQMjNkUUt4VjE5U01qODU0TzFTN2RYUWN6dw\u0026q=https%3A%2F%2Fdbourke.link%2Fweb\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":680,"length":15,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbFUwUXFrT21xalE3S0VxTmZpZmJOVXBQVmQ0QXxBQ3Jtc0tuUkpJclhxU1gxRno3bU1kSWc5TkxYaVpCak84S090VktyTTl2dnV0dml2eFFxd2tYdkJBcUpMSERua2RKaXc3ZkxYUjlxMnZ1RTIwYjVqWXh2MXh3aFJ4R0l1eGQxNkxzY0lqY1BFZVI4Mmh4QXhSTQ\u0026q=https%3A%2F%2Fwww.twitter.com%2Fmrdbourke\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbFUwUXFrT21xalE3S0VxTmZpZmJOVXBQVmQ0QXxBQ3Jtc0tuUkpJclhxU1gxRno3bU1kSWc5TkxYaVpCak84S090VktyTTl2dnV0dml2eFFxd2tYdkJBcUpMSERua2RKaXc3ZkxYUjlxMnZ1RTIwYjVqWXh2MXh3aFJ4R0l1eGQxNkxzY0lqY1BFZVI4Mmh4QXhSTQ\u0026q=https%3A%2F%2Fwww.twitter.com%2Fmrdbourke\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: mrdbourke"}}},{"startIndex":706,"length":15,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbkZVcU8tWjNVeC1uTXJiTUJsWEltcm1zcmlDUXxBQ3Jtc0tsVmNCWHdLVzhRZE0xSUlSSUVZWXNWMzlQdHBoMzc1MHhmQTF2QlBCekc3aDFkRUV5ZkcwVmhvS3FjZDVUc2RlM3RSc3JTRjAtMHh3OUVlU1Rxc0Jyai1oNFRSNUhxSTlVZlNRbW13TUhPWWx6eWZ3QQ\u0026q=https%3A%2F%2Fwww.twitch.tv%2Fmrdbourke\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbkZVcU8tWjNVeC1uTXJiTUJsWEltcm1zcmlDUXxBQ3Jtc0tsVmNCWHdLVzhRZE0xSUlSSUVZWXNWMzlQdHBoMzc1MHhmQTF2QlBCekc3aDFkRUV5ZkcwVmhvS3FjZDVUc2RlM3RSc3JTRjAtMHh3OUVlU1Rxc0Jyai1oNFRSNUhxSTlVZlNRbW13TUhPWWx6eWZ3QQ\u0026q=https%3A%2F%2Fwww.twitch.tv%2Fmrdbourke\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitch Channel Link: mrdbourke"}}},{"startIndex":754,"length":36,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0xRVkhzRC1Vd0JucTlVNE05YjBRRE44Nl9uUXxBQ3Jtc0tsMGVTbVZYNjExOFpYS2lXWS1Ybi1mdkFDRkhhTXZiM2puOWFKZDVRWEtGNlpDNjBENFhNU1RIaEc2WFpmUzNvY1owY1Rxcjc3Qk1Xb0JHOE9JWmJoMWJ5VFBuaW9NcVNYUzd1ejRpc1dicDVkdUlMSQ\u0026q=https%3A%2F%2Fdbourke.link%2Farchive-channel\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0xRVkhzRC1Vd0JucTlVNE05YjBRRE44Nl9uUXxBQ3Jtc0tsMGVTbVZYNjExOFpYS2lXWS1Ybi1mdkFDRkhhTXZiM2puOWFKZDVRWEtGNlpDNjBENFhNU1RIaEc2WFpmUzNvY1owY1Rxcjc3Qk1Xb0JHOE9JWmJoMWJ5VFBuaW9NcVNYUzd1ejRpc1dicDVkdUlMSQ\u0026q=https%3A%2F%2Fdbourke.link%2Farchive-channel\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":823,"length":31,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YSPrT2ICt9ZKd-gHKAQT_8xkl","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbHVzWW9LQW5wNXNXb00xb19YQ2xGWGVUSF91UXxBQ3Jtc0tuRnF4T3JNdnlTa3JXQi01dldhX2VZb09SR016bzgtYzJNa3FZMVBGcDE2Y09Tc01MdUlGLXZodXJYT0tSM0NVNjRGV29zVW1pdjJPeDBXSmZtelNTZC1ySEtMMkZYc0NKc1Rqa1IzeWNnTHE0Q3VEZw\u0026q=https%3A%2F%2Fdbourke.link%2Fnewsletter\u0026v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbHVzWW9LQW5wNXNXb00xb19YQ2xGWGVUSF91UXxBQ3Jtc0tuRnF4T3JNdnlTa3JXQi01dldhX2VZb09SR016bzgtYzJNa3FZMVBGcDE2Y09Tc01MdUlGLXZodXJYT0tSM0NVNjRGV29zVW1pdjJPeDBXSmZtelNTZC1ySEtMMkZYc0NKc1Rqa1IzeWNnTHE0Q3VEZw\u0026q=https%3A%2F%2Fdbourke.link%2Fnewsletter\u0026v=-jpLqtAWKfo","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":869,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=-jpLqtAWKfo","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"-jpLqtAWKfo","continuePlayback":true,"startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2es.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=fa3a4baad01629fa\u0026ip=1.208.108.242\u0026initcwndbps=3033750\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NA\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"0초"}}},{"startIndex":882,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CMYCEM2rARgBIhMIz4H37pCIkgMVenY4BR2YOS2YygEE__MZJQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=-jpLqtAWKfo\u0026t=37s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"-jpLqtAWKfo","continuePlayback":true,"startTimeSeconds":37,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2es.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=fa3a4baad01629fa\u0026ip=1.208.108.242\u0026osts=37\u0026initcwndbps=3033750\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NA\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"37초"}}},{"startIndex":904,"length":4,"onTap":{"innertubeCo | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/WebDriver | WebDriver | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web WebDriver Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 中文 (简体) WebDriver WebDriver is a remote control interface that enables introspection and control of user agents. It provides a platform- and language-neutral wire protocol as a way for out-of-process programs to remotely instruct the behavior of web browsers. To have the ability to write instruction sets that can be run interchangeably in many browsers on different platforms is critical to deliver a consistent experience to users. With the new wave of developments on the web platform, the increase diversity in devices and demands for real interoperability between the technologies, WebDriver provides tooling for cross-browser testing . Provided is a set of interfaces to discover and manipulate DOM elements in web documents and to control the behavior of a user agent. It is primarily intended to allow web authors to write tests that automate a user agent from a separate controlling process, but may also be used in such a way as to allow in-browser scripts to control a — possibly separate — browser. In this article Usage Reference Specifications See also Usage So what does WebDriver let you do and what does it look like? Since WebDriver is programming language neutral, the answer to this question depends on which WebDriver client you're using and the choice of language. But using a popular client written in Python, your interaction with WebDriver might look like this: python from selenium import webdriver from selenium.webdriver.common.by import By from selenium.webdriver.common.keys import Keys from selenium.webdriver.support.ui import WebDriverWait from selenium.webdriver.support.expected_conditions import presence_of_element_located with webdriver.Firefox() as driver: driver.get("https://google.com/ncr") wait = WebDriverWait(driver, 10) driver.find_element(By.NAME, "q").send_keys(f"cheese{Keys.RETURN}") wait.until(presence_of_element_located((By.XPATH, '//*[@id="rcnt"]'))) results = driver.find_elements(By.XPATH, "//a[@href]") for i, elem in enumerate(results): print(f'#{i} {elem.text} ({elem.get_attribute("href")})') This might produce output akin to this: #1 Cheese - Wikipedia (https://en.wikipedia.org/wiki/Cheese) Reference The WebDriver reference provides detailed information about the WebDriver API, including the available commands, capabilities, and errors. Timeouts Commands Close Window Get Element Attribute Get Element Property Get Element Tag Name Get Timeouts Get Window Handles Get Window Rect New Window Set Timeouts Set Window Rect Capabilities acceptInsecureCerts firefoxOptions webSocketUrl Errors Insecure certificate Invalid argument Invalid cookie domain Invalid selector Invalid session ID JavaScript error Script timeout Stale element reference Unknown command Unknown error Unknown method Specifications WebDriver See also Testing Selenium documentation Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jul 7, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar WebDriver Reference Timeouts Commands Close Window Get Element Attribute Get Element Property Get Element Tag Name Get Timeouts Get Window Handles Get Window Rect New Window Set Timeouts Set Window Rect Capabilities acceptInsecureCerts firefoxOptions webSocketUrl Errors Insecure certificate Invalid argument Invalid cookie domain Invalid selector Invalid session ID JavaScript error Script timeout Stale element reference Unknown command Unknown error Unknown method Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions | Browser extensions - Mozilla | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Mozilla Add-ons Browser extensions Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Browser extensions Extensions, or add-ons, can modify and enhance the capability of a browser. Extensions for Firefox are built using the WebExtensions API cross-browser technology. The technology for extensions in Firefox is, to a large extent, compatible with the extension API supported by Chromium-based browsers (such as Google Chrome, Microsoft Edge, Opera, Vivaldi). In most cases, extensions written for Chromium-based browsers run in Firefox with just a few changes . In this article Key resources Get started Concepts User interface How to Firefox workflow Reference Key resources Guides Whether you're just beginning or looking for more advanced advice, learn about how extensions work and use the WebExtensions API from our extensive range of tutorials and guides . References Get comprehensive details about the methods, properties, types, and events of the WebExtensions APIs and full details about the manifest keys . Firefox workflow Discover how to build and publish extensions for Firefox: get the lowdown on developer tools, publication and distribution, and porting on Extension Workshop . Note: If you have ideas or questions or need help, you can reach us on the community forum or in the Add-ons Room on Matrix . Get started Discover what extensions can do before building your first extension and your second extension . Learn about the anatomy of an extension and get an overview of the extension development and publication workflow, Firefox style . Explore a little deeper with a comprehensive selection of example extensions that you can run right in Firefox. Continue your learning by discovering a list of resources to follow. Concepts Get detailed information on the concepts that underpin extensions. Overview of the JavaScript API Content scripts Background scripts Match patterns Working with files Internationalization Content security policy Native messaging Native manifests User actions Differences between API implementations Chrome incompatibilities User interface Discover all the user interface components you can use in your extensions, with coding examples and tips. How to A range of tutorials to get you started on specific aspects of extension development. Intercept HTTP requests Modify a web page Safely insert external content into a page Share objects with page scripts Add a button to the toolbar Implement a settings page Work with the Tabs API Work with the Bookmarks API Work with the Cookies API Work with contextual identities Interact with the clipboard Extend the developer tools Build a cross-browser extension Firefox workflow When you are ready to create your extension for Firefox or port your Chrome extension, head over to Extension Workshop . It has details on: The Firefox workflow, such as temporarily installing extensions during development , debugging , request the right permissions , and more. The web-ext developer tool. Porting a Google Chrome extension , differences between desktop and Android , and more. Publishing and distribution overview , promoting your extension , the extension lifecycle best practices , and more. Reference JavaScript APIs Get comprehensive details about the methods, properties, types, and events for all the JavaScript APIs . There is also detailed information about the compatibility of each API with the major browsers. Most reference pages also include coding examples and links to the extension examples that use the API. Manifest keys Get full details about the manifest keys , including all their properties and settings. Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jul 17, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Browser extensions Getting started What are extensions? Your first extension Your second extension Anatomy of an extension Example extensions What next? Concepts JavaScript APIs Content scripts Background scripts Match patterns Work with files Internationalization Content Security Policy Native messaging Native manifests User actions Differences between API implementations Chrome incompatibilities User interface Toolbar button Address bar button Sidebars Context menu items Options page Extension pages Notifications Address bar suggestions devtools panels Browser styles Popups How to Intercept HTTP requests Modify a web page Insert external content Share objects with page scripts Add a button to the toolbar Implement a settings page Work with the Tabs API Work with the Bookmarks API Work with the Cookies API Work with contextual identities Interact with the clipboard Extend the developer tools Build a cross-browser extension JavaScript APIs Browser support for JavaScript APIs action alarms bookmarks browserAction browserSettings browsingData captivePortal clipboard commands contentScripts contextualIdentities cookies declarativeNetRequest devtools dns dom downloads events extension extensionTypes find history i18n identity idle management menus notifications omnibox pageAction permissions pkcs11 privacy proxy runtime scripting search sessions sidebarAction storage tabGroups tabs theme topSites types userScripts userScripts (Legacy) webNavigation webRequest windows Manifest keys action author background browser_action browser_specific_settings chrome_settings_overrides chrome_url_overrides commands content_scripts content_security_policy declarative_net_request default_locale description developer devtools_page dictionaries externally_connectable homepage_url host_permissions icons incognito manifest_version name offline_enabled Deprecated omnibox optional_host_permissions optional_permissions options_page options_ui page_action permissions protocol_handlers short_name sidebar_action storage theme theme_experiment user_scripts version version_name web_accessible_resources Extension Workshop Develop Publish Manage Enterprise Contact us Channels Add-ons blog Add-ons forum Add-ons chat Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/ios-push-template#design-template | iOS Push Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors iOS Push Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors iOS Push Template OpenAI Open in ChatGPT How to design simple iOS Push template with click action and image. OpenAI Open in ChatGPT Design Template You can design template with a simple form editor tool. You can add variables with Handlebarsjs language. You can check how the message will look in the preview section on the right side. Once designed, you can save the push notification template by clicking on Save Draft. When you are ready, you can Publish Draft by providing a name to the version. This will become the Live version, and will be used whenever the associated workflow is triggered. iOS Push notification fields description Field Description Title Small message text box. Note that this field will be displayed in single line only, and very long content can get curtailed. Use handlebarsjs to add variables. Body Large message text box. Use handlebarsjs to add variables. 📘 Note: By default, Clicking on the Notification will redirect the users to your iOS App. We’ll be soon be adding the option to add custom Action URL Adding dynamic content in iOS Push There will always be the case where you would require to add dynamic content to a template, so as to personalise it for your users. To achieve this, you can add variables in the template, which will be replaced with the dynamic content at the time of sending the message. You’ll need to pass these while triggering the communication from one of our frontend or backend SDKs. Here is a step-by-step guide on how to add dynamic content in iOS Push: 1 Declaring Variables in the global `Mock data` button If you are at this stage, it is assumed that you have declared the variables along with sample values in the global Mock data button. To see how to declare variables before using them in designing templates, refer to this section in the Templates documentation . 2 Using variables in the templates Once the variables are declared, you can use them while designing the iOS Push template. We support handlebarsjs to add variables in the template. As a general rule, all the variables have to be entered within double curly brackets: {{variable\_name}} If you have declared the variables in the global Mock data button, then they will come as auto-suggestions when you type a curly bracket { . This will remove the chances of errors like variable mismatch at the time of template rendering. Note that you will be able to enter a variable name even when you have not declared it inside the Mock data button. To manually enter the variable name, follow the handlerbarsjs guide here . Below is an example of how to enter variables in the template design. For illustration, we are using the same sample variable names that we declared in the Templates section: json Copy Ask AI { "array" : [ { "product_name" : "Aldo Sling Bag" , "product_price" : "3,950.00" }, { "product_name" : "Clarles & Keith Women Slipper, Biege, 38UK" , "product_price" : "2,549.00" }, { "product_name" : "RayBan Sunglasses" , "product_price" : "7,899.00" } ], "event" : { "location" : { "city" : "San Francisco" , "state" : "California" }, "order_id" : "11200123" , "first_name" : "Joe" }, "product_page" : "https://www.suprsend.com" } To enter a nested variable, enter in the format {{var1.var2.var3}} . E.g. to refer to city in the example above, you need to enter {{event.location.city}} To refer to an array element, enter in format {{var1.[*index*].var2}}. E.g. to refer to product_name of the first element of the array array , enter {{array.[0].product_name}}` If you have any space in the variable name, enclose it in square bracket {{event.[first name]}} You will be able to see the sample values in the Preview section, as well as in the Live version when you publish a draft. If you cannot see your variable being rendered with the sample value, check one of the following: Make sure you have entered the variable name and the sample value in the Mock data button. Make sure you have entered the correct variable name in the template, as per the handlebarsjs guideline. What happens if there is variable mismatch at the time of sending? At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user. Please note that the rest of the templates will be sent. E.g. if there is an error in rendering iOS Push template, but email template is successfully rendered, iOS Push notification will not be triggered, but email notification will be triggered by SuprSend. Was this page helpful? Yes No Suggest edits Raise issue Previous Web Push Template How to design Webpush template with customisation options to add action buttons and image. Next ⌘ I x github linkedin youtube Powered by On this page Design Template iOS Push notification fields description Adding dynamic content in iOS Push | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web | Web technology for developers | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Web technology for developers The open Web presents incredible opportunities for developers. To take full advantage of these technologies, you need to know how to use them. Below you'll find links to our Web technology documentation. In this article Documentation for Web developers Web technology references Developer tools documentation Documentation for Web developers Web developer guides The Web Developer Guides provide practical, how-to content to help you use Web technologies for your goals or needs. Tutorials for Web developers Tutorials to take you step-by-step through learning HTML, CSS, JavaScript, and Web APIs. Accessibility Enabling as many people as possible to use websites, even when those people's abilities are limited in some way. Performance Making content as available and interactive as possible, as soon as possible. Privacy Protecting users' personal data. Security Protecting users from data leaks and data theft, side-channel attacks, and attacks such as cross-site scripting, content injection, and click-jacking. Glossary Definitions of Web-related terms. Web technology references Web APIs JavaScript programming APIs you can use to build apps on the Web. HTML HTML provides the fundamental building blocks for structuring Web documents and apps. CSS Cascading Style Sheets are used to describe the appearance of Web documents and apps. JavaScript JavaScript is the Web's native programming language. WebAssembly WebAssembly allows programs written in C, C++, Rust, Swift, C#, Go, and more to run on the Web. HTTP HTTP is the fundamental Internet protocol for fetching documents, stylesheets, scripts, images, videos, fonts, and other resources over the Web — and for sending data back to Web servers. Media Formats, codecs, protocols, APIs, and techniques for embedding and streaming video, audio, and image content in Web documents and apps. SVG Scalable Vector Graphics lets you create images that scale smoothly to any size. MathML MathML lets you display complex mathematical notation on the Web. URI Uniform Resource Identifiers are used by various technologies, including the browser itself via the address bar, to identify resources in various ways. WebDriver WebDriver is a browser-automation mechanism for remotely controlling a browser by emulating the actions of a real person using the browser. It's widely used for cross-browser testing of Web apps. Web Extensions Web Extensions are a way for you to give users enhanced capabilities in their browsers — for doing things such as blocking ads and other content, customizing the appearance of pages, and more. Web App Manifests Web App Manifests let you enable users to install Web apps to their device home screens, with aspects such as portrait/landscape screen orientation and display mode (e.g., full screen) pre-set. Progressive Web Apps (PWAs) Progressive Web Apps provide a user experience similar to native mobile apps. OpenSearch OpenSearch allows a website to describe a search engine for itself, so that a browser or other client application can use that search engine. XML The Extensible Markup Language is a strict serialization of the Document Object Model . XSLT Extensible Stylesheet Language Transformations is an XML -based language used, in conjunction with specialized processing software, for the transformation of XML documents. XPath XPath uses a non-XML syntax to provide a flexible way of addressing (pointing to) different parts of an XML document. It can also be used to test addressed nodes within a document to determine whether they match a pattern or not. EXSLT EXSLT a set of extensions to XSLT . Developer tools documentation Firefox Developer Tools Documentation for the set of web-developer tools built into Firefox. Chrome DevTools Documentation for the set of web-developer tools built into Chrome. Safari Web Inspector Documentation for the set of web-developer tools built into Safari. Edge DevTools Documentation for the set of web-developer tools built into Edge. Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jul 29, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Web documentation Accessibility CSS HTML HTTP JavaScript MathML Media Performance Privacy on the web Progressive web apps Security SVG URIs Web APIs WebDriver XML Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://dev.to/t/wlhchallenge | World's Largest Hackathon Writing Challenge - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close World's Largest Hackathon Writing Challenge Follow Hide This is the official tag for submissions and announcements related to the World's Largest Hackathon Writing Challenge Create Post Older #wlhchallenge posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Bolt Made me Bold... (LullaRead) WLH Challenge: After the Hack Submission Aima Atigari Aima Atigari Aima Atigari Follow Sep 5 '25 Bolt Made me Bold... (LullaRead) # devchallenge # wlhchallenge # career # entrepreneurship 6 reactions Comments Add Comment 4 min read Wired for Innovation: Lessons from Bolt.New hackathon WLH Challenge: Beyond the Code Submission EcoGetaway EcoGetaway EcoGetaway Follow Jul 23 '25 Wired for Innovation: Lessons from Bolt.New hackathon # devchallenge # wlhchallenge # community # networking Comments Add Comment 2 min read NoChill.AI – Built During Exams, Celebrated With a Community WLH Challenge: Beyond the Code Submission T Mohamed Yaser T Mohamed Yaser T Mohamed Yaser Follow Jul 23 '25 NoChill.AI – Built During Exams, Celebrated With a Community # devchallenge # wlhchallenge # community # networking Comments Add Comment 2 min read 🛠️ After the Hack: What’s Next for Promptle (and Me) WLH Challenge: After the Hack Submission Nithya Subramaniam Nithya Subramaniam Nithya Subramaniam Follow Jul 22 '25 🛠️ After the Hack: What’s Next for Promptle (and Me) # devchallenge # wlhchallenge # career # entrepreneurship Comments Add Comment 2 min read built TailorMyResume.online Magic with Bolt.new WLH Challenge: Building with Bolt Submission yu gumin yu gumin yu gumin Follow Jul 21 '25 built TailorMyResume.online Magic with Bolt.new # devchallenge # wlhchallenge # bolt # ai Comments Add Comment 2 min read Not Sure What Therapy’s Right for You? There’s a Quiz for That | MindFLTR WLH Challenge: Beyond the Code Submission Sola Janet Browne Sola Janet Browne Sola Janet Browne Follow Jul 23 '25 Not Sure What Therapy’s Right for You? There’s a Quiz for That | MindFLTR # devchallenge # wlhchallenge # community # networking 4 reactions Comments 1 comment 4 min read 🌱 Building Roots: Voice-First School System with ElevenLabs WLH Challenge: Building with Bolt Submission Juan González Ponce Juan González Ponce Juan González Ponce Follow Jul 23 '25 🌱 Building Roots: Voice-First School System with ElevenLabs # devchallenge # wlhchallenge # bolt # ai 5 reactions Comments Add Comment 3 min read HomeWhisper: Beyond the Code – Building a Human-Centered Smart Home Experience WLH Challenge: Beyond the Code Submission ANIRUDDHA ADAK ANIRUDDHA ADAK ANIRUDDHA ADAK Follow Jul 17 '25 HomeWhisper: Beyond the Code – Building a Human-Centered Smart Home Experience # devchallenge # wlhchallenge # community # networking Comments Add Comment 2 min read Beyond the Code - The Intense Human Story of StudentSphere's Genesis WLH Challenge: Beyond the Code Submission Abdulahad Ishaq Abdulahad Ishaq Abdulahad Ishaq Follow Jul 17 '25 Beyond the Code - The Intense Human Story of StudentSphere's Genesis # wlhchallenge # bolt # supabase # hackathon 1 reaction Comments Add Comment 3 min read Life After WLH - How a Hackathon Transformed My Career Trajectory Oni Oni Oni Follow Jul 16 '25 Life After WLH - How a Hackathon Transformed My Career Trajectory # devchallenge # wlhchallenge # career # entrepreneurship Comments Add Comment 1 min read From Solo Developer to Community Builder - My WLH Journey Beyond Code Oni Oni Oni Follow Jul 16 '25 From Solo Developer to Community Builder - My WLH Journey Beyond Code # devchallenge # wlhchallenge # community # networking Comments Add Comment 1 min read Code Guardian: Revolutionizing Code Review with AI and Bolt WLH Challenge: Building with Bolt Submission ANIRUDDHA ADAK ANIRUDDHA ADAK ANIRUDDHA ADAK Follow Jul 14 '25 Code Guardian: Revolutionizing Code Review with AI and Bolt # devchallenge # wlhchallenge # bolt # ai Comments Add Comment 1 min read My Project Development Experience and Technical Journey with TrailGuard Daniela Oliveira Daniela Oliveira Daniela Oliveira Follow Jul 13 '25 My Project Development Experience and Technical Journey with TrailGuard # devchallenge # wlhchallenge # bolt # ai Comments Add Comment 2 min read ResearchFlow AI: Helping Students Navigate the Research Maze WLH Challenge: Beyond the Code Submission FranP-code FranP-code FranP-code Follow Jul 17 '25 ResearchFlow AI: Helping Students Navigate the Research Maze # devchallenge # wlhchallenge # community # networking Comments Add Comment 3 min read MindCare AI: Revolutionizing Mental Health Support with Compassionate AI WLH Challenge: Beyond the Code Submission ANIRUDDHA ADAK ANIRUDDHA ADAK ANIRUDDHA ADAK Follow Jul 11 '25 MindCare AI: Revolutionizing Mental Health Support with Compassionate AI # devchallenge # wlhchallenge # community # networking Comments Add Comment 3 min read Self-Learning MCP Ecosystem - System Specification: Building with Bolt - WLH Challenge WLH Challenge: Building with Bolt Submission Arion Dev.ed Arion Dev.ed Arion Dev.ed Follow Aug 9 '25 Self-Learning MCP Ecosystem - System Specification: Building with Bolt - WLH Challenge # devchallenge # wlhchallenge # bolt # ai 14 reactions Comments 1 comment 2 min read From Law School to LegalTech: How I built Speedy Justice WLH Challenge: Building with Bolt Submission Manvi Manvi Manvi Follow Jul 9 '25 From Law School to LegalTech: How I built Speedy Justice # devchallenge # buildingwithbolt # bolt # wlhchallenge Comments Add Comment 2 min read Iggy: After the Hack - WLH Challenge WLH Challenge: After the Hack Submission Arion Dev.ed Arion Dev.ed Arion Dev.ed Follow Aug 9 '25 Iggy: After the Hack - WLH Challenge # devchallenge # wlhchallenge # career # entrepreneurship 9 reactions Comments Add Comment 3 min read Bankrupt Clock: After the Hack - WLH Challenge WLH Challenge: After the Hack Submission Arion Dev.ed Arion Dev.ed Arion Dev.ed Follow Aug 9 '25 Bankrupt Clock: After the Hack - WLH Challenge # devchallenge # wlhchallenge # career # entrepreneurship 11 reactions Comments Add Comment 3 min read Celebrate!: After the Hack - WLH Challenge WLH Challenge: After the Hack Submission Arion Dev.ed Arion Dev.ed Arion Dev.ed Follow Aug 9 '25 Celebrate!: After the Hack - WLH Challenge # devchallenge # wlhchallenge # career # entrepreneurship 9 reactions Comments Add Comment 3 min read 🚀Building with Bolt: How I Created Smile2Earn WLH Challenge: Building with Bolt Submission Shree chavan Shree chavan Shree chavan Follow Jul 9 '25 🚀Building with Bolt: How I Created Smile2Earn # devchallenge # wlhchallenge # bolt # ai Comments Add Comment 2 min read 3D game created with AI WLH Challenge: Building with Bolt Submission Mykola Korzh Mykola Korzh Mykola Korzh Follow Jul 31 '25 3D game created with AI # wlhchallenge # devchallenge # ai # bolt 26 reactions Comments 2 comments 5 min read What's next after the Bolt hackathon WLH Challenge: After the Hack Submission goldenekpendu goldenekpendu goldenekpendu Follow Aug 1 '25 What's next after the Bolt hackathon # devchallenge # wlhchallenge # career # entrepreneurship 19 reactions Comments Add Comment 2 min read The Art of the Hack: From Suspicion to Submission WLH Challenge: After the Hack Submission NiKole Maxwell NiKole Maxwell NiKole Maxwell Follow Aug 1 '25 The Art of the Hack: From Suspicion to Submission # devchallenge # wlhchallenge # bolt # ai 15 reactions Comments Add Comment 3 min read From MVP to Impact: What’s Next for Soulvia? WLH Challenge: After the Hack Submission hannalap hannalap hannalap Follow Jul 31 '25 From MVP to Impact: What’s Next for Soulvia? # devchallenge # wlhchallenge # career # entrepreneurship 18 reactions Comments Add Comment 3 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/react-webpush | WebPush - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK SuprSend Client SDK Authentication Javascript Android iOS React Native Flutter React SDK Integration WebPush Preferences Events and User methods InApp Feed Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation React WebPush Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog React WebPush OpenAI Open in ChatGPT Integration steps of webpush in react application. OpenAI Open in ChatGPT Integration steps 1 Integration of SuprSendProvider Please follow this guide to integrate SuprSendProvider in your application. Pass vapidKey prop to SuprSendProvider . You can find it in SuprSendDashboard --> Vendors --> WebPush . 2 Add ServiceWorker file Service worker file is the background worker script which handles push notifications. Create serviceworker.js file such that it should be publicly accessible from https://<your_domain>/serviceworker.js . If you want to customise this default service worker file name serviceworker.js to other file, pass swFileName prop to SuprSendProvider . Add below lines of code in that service worker file and replace YOUR_PUBLIC_API_KEY with key you find in API Keys page in SuprSend Dashboard. serviceworker.js Copy Ask AI importScripts ( 'https://cdn.jsdelivr.net/npm/@suprsend/ [email protected] /public/serviceworker.min.js' ); initSuprSend ( YOUR_PUBLIC_API_KEY ); // replace publicApiKey with your value 3 Accessing webpush methods using useSuprSendClient hook All available webpush methods can be accessed using SuprSend client instance. You can get the SuprSend client instance using useSuprSendClient hook. 4 Register Push Call registerPush in your code, which will perform following tasks: Ask for notification permission. Register push service and generate webpush token. Send webpush token to SuprSend. TypeScript Copy Ask AI const response = await suprSendClient . webpush . registerPush (); Returns: Promise<ApiResponse> NOTE: This method should be called on user action like button click for better UX, don’t call this on page load. Other available methods Check for permission To check if user has enabled notifications permission use method provided by library Copy Ask AI suprSendClient . webpush . notificationPermission (): This will return a string representing the current permission. The value can be: granted: The user has granted permission for the current origin to display notifications. denied: The user has denied permission for the current origin to display notifications. default: The user’s decision is unknown. This will be permission when user first lands on website. Was this page helpful? Yes No Suggest edits Raise issue Previous Preferences Step-by-Step Guide to add SuprSend notification preference centre in react-based websites. Next ⌘ I x github linkedin youtube Powered by On this page Integration steps Other available methods Check for permission | 2026-01-13T08:48:25 |
http://www.robertjkhoury.com/ | Robert J. Khoury 0 Skip to Content About Books Newsletter Reviews Media Speeches & Podcasts @internvsmanager @robertkhouryauthor Robert J. Khoury Login Account Contact Open Menu Close Menu About Books Newsletter Reviews Media Speeches & Podcasts @internvsmanager @robertkhouryauthor Robert J. Khoury Login Account Contact Open Menu Close Menu About Books Newsletter Reviews Folder: Media Back Speeches & Podcasts @internvsmanager @robertkhouryauthor Login Account Contact Robert J. Khoury Author | Intern Manager | Executive Buy Now Buy Now Robert J. Khoury Author and CEO Agile Rainmakers, LLC agilerainmakers.com Want more? Subscribe to my newsletter! Sign up for news and updates as Rob continues to transform the landscape of modern internships: First Name Last Name Email Address Sign Up Share your email info with someone else? Never. Scout’s honor. Thanks for signing up! You should have a note from me in your inbox soon. Meanwhile, have an awesome day. Contact ABOUT | BOOKS | MEDIA | NEWSLETTER | REVIEWS | CONTACT © 2023 Agile Rainmakers | 2026-01-13T08:48:25 |
https://youtu.be/haCv-oXOuko | The Disruptive Power of Artificial Intelligence - ML 100 - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0xb599ecc3368de40f"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"Cgt1NUJndGxMR2VndyjXjZjLBjIKCgJLUhIEGgAgFGLfAgrcAjE1LllUPVZUVUJubFN0Q08yYUJMRzJWcjVOVl9TWGJFWnljajZkeFY4WU1yMEdLNHJmZlg2SlRuTUt6MW94WVdiYmZIc2NaR2tzLVdtSkpnMUZCa2NpN2xMWU9VNkU2dGxsZTFQM1RUU0huZkZURHp6bEFpSWNUX0cwYUx4ZzlMY2xaZG0xNnAxTGdadjU5d3pJT2Z3c19SY3B1U2VVTzFXc3I0V2puUm0xZUppWTh6aXg2WDJuOGRBc3V3R05MQXQwMUw0aWFMdkczMTZQQjhiMDl6c2lLYm5OdDBnRlpJa3BueEdQV0pxdmhGVVBuRUlNWmg0eEdhTHl4SnM3TFpkSjhoUEtMb1RGX251aDdKalFmaG5nOXRlemFuOHlJNnlad3pVRWxnUE1LaXJXakF5WF9kUDdfUVZHU2MwaFdmeWEzc1dsNFQ1a3BtU0R4SWk1eHdJbEx5SS03QQ%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRj3VaE4_f8Ldg0stX8lzJ88MqUyiOUw84MjHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","videoDescriptionCourseSectionRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","topicLinkRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"Cgt1NUJndGxMR2VndyjXjZjLBjIKCgJLUhIEGgAgFGLfAgrcAjE1LllUPVZUVUJubFN0Q08yYUJMRzJWcjVOVl9TWGJFWnljajZkeFY4WU1yMEdLNHJmZlg2SlRuTUt6MW94WVdiYmZIc2NaR2tzLVdtSkpnMUZCa2NpN2xMWU9VNkU2dGxsZTFQM1RUU0huZkZURHp6bEFpSWNUX0cwYUx4ZzlMY2xaZG0xNnAxTGdadjU5d3pJT2Z3c19SY3B1U2VVTzFXc3I0V2puUm0xZUppWTh6aXg2WDJuOGRBc3V3R05MQXQwMUw0aWFMdkczMTZQQjhiMDl6c2lLYm5OdDBnRlpJa3BueEdQV0pxdmhGVVBuRUlNWmg0eEdhTHl4SnM3TFpkSjhoUEtMb1RGX251aDdKalFmaG5nOXRlemFuOHlJNnlad3pVRWxnUE1LaXJXakF5WF9kUDdfUVZHU2MwaFdmeWEzc1dsNFQ1a3BtU0R4SWk1eHdJbEx5SS03QQ%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwjfqfzukIiSAxXdRDgFHdpIGmYyDHJlbGF0ZWQtYXV0b0jK9LquqP-r0IUBmgEFCAMQ-B3KAQSu-h5C","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=Z_c4byLrNBU\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"Z_c4byLrNBU","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjfqfzukIiSAxXdRDgFHdpIGmYyDHJlbGF0ZWQtYXV0b0jK9LquqP-r0IUBmgEFCAMQ-B3KAQSu-h5C","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=Z_c4byLrNBU\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"Z_c4byLrNBU","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjfqfzukIiSAxXdRDgFHdpIGmYyDHJlbGF0ZWQtYXV0b0jK9LquqP-r0IUBmgEFCAMQ-B3KAQSu-h5C","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=Z_c4byLrNBU\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"Z_c4byLrNBU","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"The Disruptive Power of Artificial Intelligence - ML 100"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 127회"},"shortViewCount":{"simpleText":"조회수 127회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CJECELW0CRgAIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC2hhQ3Ytb1hPdWtvGmBFZ3RvWVVOMkxXOVlUM1ZyYjBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDJoaFEzWXRiMWhQZFd0dkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CJECELW0CRgAIhMI36n87pCIkgMV3UQ4BR3aSBpm"}}],"trackingParams":"CJECELW0CRgAIhMI36n87pCIkgMV3UQ4BR3aSBpm","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"1","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJwCEKVBIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},{"innertubeCommand":{"clickTrackingParams":"CJwCEKVBIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJ0CEPqGBCITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJ0CEPqGBCITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"haCv-oXOuko"},"likeParams":"Cg0KC2hhQ3Ytb1hPdWtvIAAyDAjXjZjLBhC7ssS1Ag%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CJ0CEPqGBCITCN-p_O6QiJIDFd1EOAUd2kgaZg=="}}}}}}}]}},"accessibilityText":"다른 사용자 1명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJwCEKVBIhMI36n87pCIkgMV3UQ4BR3aSBpm","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"2","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJsCEKVBIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},{"innertubeCommand":{"clickTrackingParams":"CJsCEKVBIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"haCv-oXOuko"},"removeLikeParams":"Cg0KC2hhQ3Ytb1hPdWtvGAAqDAjXjZjLBhD6ycW1Ag%3D%3D"}}}]}},"accessibilityText":"다른 사용자 1명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJsCEKVBIhMI36n87pCIkgMV3UQ4BR3aSBpm","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CJECELW0CRgAIhMI36n87pCIkgMV3UQ4BR3aSBpm","isTogglingDisabled":true}},"likeStatusEntityKey":"EgtoYUN2LW9YT3VrbyA-KAE%3D","likeStatusEntity":{"key":"EgtoYUN2LW9YT3VrbyA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJkCEKiPCSITCN-p_O6QiJIDFd1EOAUd2kgaZg=="}},{"innertubeCommand":{"clickTrackingParams":"CJkCEKiPCSITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJoCEPmGBCITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJoCEPmGBCITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"haCv-oXOuko"},"dislikeParams":"Cg0KC2hhQ3Ytb1hPdWtvEAAiDAjXjZjLBhDytce1Ag%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CJoCEPmGBCITCN-p_O6QiJIDFd1EOAUd2kgaZg=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJkCEKiPCSITCN-p_O6QiJIDFd1EOAUd2kgaZg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJgCEKiPCSITCN-p_O6QiJIDFd1EOAUd2kgaZg=="}},{"innertubeCommand":{"clickTrackingParams":"CJgCEKiPCSITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"haCv-oXOuko"},"removeLikeParams":"Cg0KC2hhQ3Ytb1hPdWtvGAAqDAjXjZjLBhDO2se1Ag%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJgCEKiPCSITCN-p_O6QiJIDFd1EOAUd2kgaZg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CJECELW0CRgAIhMI36n87pCIkgMV3UQ4BR3aSBpm","isTogglingDisabled":true}},"dislikeEntityKey":"EgtoYUN2LW9YT3VrbyA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgtoYUN2LW9YT3VrbyD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJYCEOWWARgDIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},{"innertubeCommand":{"clickTrackingParams":"CJYCEOWWARgDIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtoYUN2LW9YT3Vrb6ABAQ%3D%3D","commands":[{"clickTrackingParams":"CJYCEOWWARgDIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CJcCEI5iIhMI36n87pCIkgMV3UQ4BR3aSBpm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJYCEOWWARgDIhMI36n87pCIkgMV3UQ4BR3aSBpm","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CJQCEOuQCSITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJUCEPuGBCITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DhaCv-oXOuko\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJUCEPuGBCITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=haCv-oXOuko","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"haCv-oXOuko","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2lk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=85a0affa85ceba4a\u0026ip=1.208.108.242\u0026initcwndbps=4306250\u0026mt=1768293891\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CJUCEPuGBCITCN-p_O6QiJIDFd1EOAUd2kgaZg=="}}}}}},"trackingParams":"CJQCEOuQCSITCN-p_O6QiJIDFd1EOAUd2kgaZg=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJICEOuQCSITCN-p_O6QiJIDFd1EOAUd2kgaZg=="}},{"innertubeCommand":{"clickTrackingParams":"CJICEOuQCSITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJMCEPuGBCITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DhaCv-oXOuko\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJMCEPuGBCITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=haCv-oXOuko","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"haCv-oXOuko","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2lk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=85a0affa85ceba4a\u0026ip=1.208.108.242\u0026initcwndbps=4306250\u0026mt=1768293891\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CJMCEPuGBCITCN-p_O6QiJIDFd1EOAUd2kgaZg=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJICEOuQCSITCN-p_O6QiJIDFd1EOAUd2kgaZg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CJECELW0CRgAIhMI36n87pCIkgMV3UQ4BR3aSBpm","superTitleLink":{"runs":[{"text":"Adventures in Machine Learning","navigationEndpoint":{"clickTrackingParams":"CJECELW0CRgAIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLJesql-aSfX4uEqPA7SS_VC-wnQXhvZV7","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLJesql-aSfX4uEqPA7SS_VC-wnQXhvZV7"}}}]},"dateText":{"simpleText":"2023. 1. 19."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"2년 전"}},"simpleText":"2년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Top End Devs","navigationEndpoint":{"clickTrackingParams":"CJACEOE5IhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"url":"/@TopEndDevs","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCABJEQ57MIn6X3TIHIebJUw","canonicalBaseUrl":"/@TopEndDevs"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CJACEOE5IhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"url":"/@TopEndDevs","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCABJEQ57MIn6X3TIHIebJUw","canonicalBaseUrl":"/@TopEndDevs"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 4.5천명"}},"simpleText":"구독자 4.5천명"},"trackingParams":"CJACEOE5IhMI36n87pCIkgMV3UQ4BR3aSBpm"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCABJEQ57MIn6X3TIHIebJUw","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CIICEJsrIhMI36n87pCIkgMV3UQ4BR3aSBpmKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Top End Devs을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Top End Devs을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CI8CEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CI4CEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CIcCEJf5ASITCN-p_O6QiJIDFd1EOAUd2kgaZg==","command":{"clickTrackingParams":"CIcCEJf5ASITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CIcCEJf5ASITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CI0CEOy1BBgDIhMI36n87pCIkgMV3UQ4BR3aSBpmMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQSu-h5C","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ0FCSkVRNTdNSW42WDNUSUhJZWJKVXcSAggBGAAgBFITCgIIAxILaGFDdi1vWE91a28YAA%3D%3D"}},"trackingParams":"CI0CEOy1BBgDIhMI36n87pCIkgMV3UQ4BR3aSBpm","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CIwCEO21BBgEIhMI36n87pCIkgMV3UQ4BR3aSBpmMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQSu-h5C","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ0FCSkVRNTdNSW42WDNUSUhJZWJKVXcSAggDGAAgBFITCgIIAxILaGFDdi1vWE91a28YAA%3D%3D"}},"trackingParams":"CIwCEO21BBgEIhMI36n87pCIkgMV3UQ4BR3aSBpm","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CIgCENuLChgFIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CIgCENuLChgFIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CIkCEMY4IhMI36n87pCIkgMV3UQ4BR3aSBpm","dialogMessages":[{"runs":[{"text":"Top End Devs"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CIsCEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmMgV3YXRjaMoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCABJEQ57MIn6X3TIHIebJUw"],"params":"CgIIAxILaGFDdi1vWE91a28YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CIsCEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CIoCEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CIgCENuLChgFIhMI36n87pCIkgMV3UQ4BR3aSBpm"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CIICEJsrIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CIYCEP2GBCITCN-p_O6QiJIDFd1EOAUd2kgaZjIJc3Vic2NyaWJlygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DhaCv-oXOuko%26continue_action%3DQUFFLUhqazRTSHpBRng5bjd6NXBiMjd2Mm1wNEZjWUZxUXxBQ3Jtc0tsNEJpWHdsQmp0Q0xzRGV2VjBia1lJMGVOVzBkRkY0dWNDdkVmSUhHTDhPMWZfZlNRd21EbUQyaDZvc1YwRHNyeE1Idm5ScDg0U2NrNDJpWnZKQ25YeVhFTXJTVTZES2d3OVlNWVU3X0phSlc4VER6ZDgwdk5BSDB4cXMxUW9yREV3V3VpdllOTktxbmRSLXRiV1BNS0d5VXhtUGRtVEtrcXhsZVltNXd3TWxfNUdLT3FiOUJSLUtyYmVXZUdlZ1ZmZ0Jramg\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CIYCEP2GBCITCN-p_O6QiJIDFd1EOAUd2kgaZsoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=haCv-oXOuko","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"haCv-oXOuko","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2lk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=85a0affa85ceba4a\u0026ip=1.208.108.242\u0026initcwndbps=4306250\u0026mt=1768293891\u0026oweuc="}}}}},"continueAction":"QUFFLUhqazRTSHpBRng5bjd6NXBiMjd2Mm1wNEZjWUZxUXxBQ3Jtc0tsNEJpWHdsQmp0Q0xzRGV2VjBia1lJMGVOVzBkRkY0dWNDdkVmSUhHTDhPMWZfZlNRd21EbUQyaDZvc1YwRHNyeE1Idm5ScDg0U2NrNDJpWnZKQ25YeVhFTXJTVTZES2d3OVlNWVU3X0phSlc4VER6ZDgwdk5BSDB4cXMxUW9yREV3V3VpdllOTktxbmRSLXRiV1BNS0d5VXhtUGRtVEtrcXhsZVltNXd3TWxfNUdLT3FiOUJSLUtyYmVXZUdlZ1ZmZ0Jramg","idamTag":"66429"}},"trackingParams":"CIYCEP2GBCITCN-p_O6QiJIDFd1EOAUd2kgaZg=="}}}}}},"subscribedEntityKey":"EhhVQ0FCSkVRNTdNSW42WDNUSUhJZWJKVXcgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CIICEJsrIhMI36n87pCIkgMV3UQ4BR3aSBpmKPgdMgV3YXRjaMoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCABJEQ57MIn6X3TIHIebJUw"],"params":"EgIIAxgAIgtoYUN2LW9YT3Vrbw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CIICEJsrIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CIICEJsrIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CIMCEMY4IhMI36n87pCIkgMV3UQ4BR3aSBpm","dialogMessages":[{"runs":[{"text":"Top End Devs"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CIUCEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmKPgdMgV3YXRjaMoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCABJEQ57MIn6X3TIHIebJUw"],"params":"CgIIAxILaGFDdi1vWE91a28YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CIUCEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CIQCEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CIECEM2rARgBIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CIECEM2rARgBIhMI36n87pCIkgMV3UQ4BR3aSBpm","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CIECEM2rARgBIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CIECEM2rARgBIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CIECEM2rARgBIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CIECEM2rARgBIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Have you ever wondered about the most promising industries in Machine Learning? Today we will learn from Avi Goldfarb, the chair of AI at the University of Toronto, about...\n\n-The most promising AI industries\n-Potential problems with powerful AI\n-The economics behind innovation\n\nhttps://topenddevs.com/podcasts/adven...","commandRuns":[{"startIndex":280,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CIECEM2rARgBIhMI36n87pCIkgMV3UQ4BR3aSBpmSMr0uq6o_6vQhQHKAQSu-h5C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbGtRT0JuWXlnU1BMbjlLeXVyUkNwU0VFRzNiQXxBQ3Jtc0tuWG9Qbm1jVllNQlZOYXAxTzNVdUVBVkhpUE1uOUhCNzlwMWVoeGZ5ZHpDWTBHdDJzbVRIX0p1YW1GOHR5Y2dGWXVmX1JSVkpBd05fR1FoRFpLeTBJclRXOVpXV18wSkwzVmVpdkNjSXJpSGdWUHNIcw\u0026q=https%3A%2F%2Ftopenddevs.com%2Fpodcasts%2Fadventures-in-machine-learning%2Fepisodes%2Fthe-disruptive-power-of-artificial-intelligence-ml-100\u0026v=haCv-oXOuko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbGtRT0JuWXlnU1BMbjlLeXVyUkNwU0VFRzNiQXxBQ3Jtc0tuWG9Qbm1jVllNQlZOYXAxTzNVdUVBVkhpUE1uOUhCNzlwMWVoeGZ5ZHpDWTBHdDJzbVRIX0p1YW1GOHR5Y2dGWXVmX1JSVkpBd05fR1FoRFpLeTBJclRXOVpXV18wSkwzVmVpdkNjSXJpSGdWUHNIcw\u0026q=https%3A%2F%2Ftopenddevs.com%2Fpodcasts%2Fadventures-in-machine-learning%2Fepisodes%2Fthe-disruptive-power-of-artificial-intelligence-ml-100\u0026v=haCv-oXOuko","target":"TARGET_NEW_WINDOW","nofollow":true}}}}],"styleRuns":[{"startIndex":0,"length":280,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":280,"length":40,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":280,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":280,"length":40,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CIACELsvGAMiEwjfqfzukIiSAxXdRDgFHdpIGmbKAQSu-h5C","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/next"}},"continuationCommand":{"token":"Eg0SC2hhQ3Ytb1hPdWtvGAYyJSIRIgtoYUN2LW9YT3VrbzAAeAJCEGNvbW1lbnRzLXNlY3Rpb24%3D","request":"CONTINUATION_REQUEST_TYPE_WATCH_NEXT"}}}}],"trackingParams":"CIACELsvGAMiEwjfqfzukIiSAxXdRDgFHdpIGmY=","sectionIdentifier":"comment-item-section","targetId":"comments-section"}}],"trackingParams":"CP8BELovIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/MiUHjLxm3V0/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBo1Hv5RTXsmjvlqNNZVC-wrQi3wQ","width":168,"height":94},{"url":"https://i.ytimg.com/vi/MiUHjLxm3V0/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDMHaxvD6EebagtNAlCHG_hE5vuJA","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"55:00","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"MiUHjLxm3V0","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"55분"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CP4BEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"MiUHjLxm3V0","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CP4BEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CP0BEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"MiUHjLxm3V0"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CP0BEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CPYBENTEDBgAIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CPwBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPwBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"MiUHjLxm3V0","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPwBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["MiUHjLxm3V0"],"params":"CAQ%3D"}},"videoIds":["MiUHjLxm3V0"],"videoCommand":{"clickTrackingParams":"CPwBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=MiUHjLxm3V0\u0026pp=ugUEEgJlbg%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"MiUHjLxm3V0","playerParams":"ugUEEgJlbg%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2zk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=3225078cbc66dd5d\u0026ip=1.208.108.242\u0026initcwndbps=4163750\u0026mt=1768293891\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPwBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPsBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CPYBENTEDBgAIhMI36n87pCIkgMV3UQ4BR3aSBpm"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"The World's Most Important Machine"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/7vCbvtCqtjQ3YLgsJt7Y952MQV1sBvhllSCSxHP8_sVZdcPCBrITfhkN2RdyCuwPnsByq-1GoA=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"Veritasium 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPYBENTEDBgAIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"url":"/@veritasium","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCHnyfMqiRRG1u-2MsSQLbXA","canonicalBaseUrl":"/@veritasium"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"Veritasium","styleRuns":[{"startIndex":10,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4289374890},{"key":"USER_INTERFACE_THEME_LIGHT","value":4284506208}]}}}],"attachmentRuns":[{"startIndex":10,"length":0,"element":{"type":{"imageType":{"image":{"sources":[{"clientResource":{"imageName":"CHECK_CIRCLE_FILLED"},"width":14,"height":14}]}}},"properties":{"layoutProperties":{"height":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"width":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"margin":{"left":{"value":4,"unit":"DIMENSION_UNIT_POINT"}}}}},"alignment":"ALIGNMENT_VERTICAL_CENTER"}]}}]},{"metadataParts":[{"text":{"content":"조회수 1328만회"}},{"text":{"content":"12일 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CPcBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CPoBEP6YBBgAIhMI36n87pCIkgMV3UQ4BR3aSBpm","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPoBEP6YBBgAIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPoBEP6YBBgAIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"MiUHjLxm3V0","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPoBEP6YBBgAIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["MiUHjLxm3V0"],"params":"CAQ%3D"}},"videoIds":["MiUHjLxm3V0"],"videoCommand":{"clickTrackingParams":"CPoBEP6YBBgAIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=MiUHjLxm3V0\u0026pp=ugUEEgJlbg%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"MiUHjLxm3V0","playerParams":"ugUEEgJlbg%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2zk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=3225078cbc66dd5d\u0026ip=1.208.108.242\u0026initcwndbps=4163750\u0026mt=1768293891\u0026oweuc="}}}}}}}]}}}}}}},{"listItemViewModel":{"title":{"content":"재생목록에 저장"},"leadingImage":{"sources":[{"clientResource":{"imageName":"BOOKMARK_BORDER"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CPkBEJSsCRgBIhMI36n87pCIkgMV3UQ4BR3aSBpm","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPkBEJSsCRgBIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPkBEJSsCRgBIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtNaVVIakx4bTNWMA%3D%3D"}}}}}}}}}}},{"listItemViewModel":{"title":{"content":"공유"},"leadingImage":{"sources":[{"clientResource":{"imageName":"SHARE"}}]},"rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPcBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtNaVVIakx4bTNWMA%3D%3D","commands":[{"clickTrackingParams":"CPcBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CPgBEI5iIhMI36n87pCIkgMV3UQ4BR3aSBpm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}}}}}]}}}}}}}},"accessibilityText":"추가 작업","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CPcBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm","type":"BUTTON_VIEW_MODEL_TYPE_TEXT","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}},"contentId":"MiUHjLxm3V0","contentType":"LOCKUP_CONTENT_TYPE_VIDEO","rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CPYBENTEDBgAIhMI36n87pCIkgMV3UQ4BR3aSBpm","visibility":{"types":"12"}}},"accessibilityContext":{"label":"The World's Most Important Machine 55분"},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPYBENTEDBgAIhMI36n87pCIkgMV3UQ4BR3aSBpmMgdyZWxhdGVkSMr0uq6o_6vQhQGaAQUIARD4HcoBBK76HkI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=MiUHjLxm3V0\u0026pp=ugUEEgJlbg%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"MiUHjLxm3V0","playerParams":"ugUEEgJlbg%3D%3D","nofollow":true,"ustreamerConfig":"KgYKBBICZW4=","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2zk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026oreouc=1\u0026id=3225078cbc66dd5d\u0026ip=1.208.108.242\u0026initcwndbps=4163750\u0026mt=1768293891\u0026oweuc="}}}}}}}}}},{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/Kr3Sh2PKA8Y/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLCXd5o9SPPtx6AleW6xZ8nk5GRRQQ","width":168,"height":94},{"url":"https://i.ytimg.com/vi/Kr3Sh2PKA8Y/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDz1NjcApJlOHDuo56ty6wCaCRyvg","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"31:48","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"Kr3Sh2PKA8Y","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"31분 48초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CPUBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"Kr3Sh2PKA8Y","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPUBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CPQBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpmygEErvoeQg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"Kr3Sh2PKA8Y"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPQBEPBbIhMI36n87pCIkgMV3UQ4BR3aSBpm","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CO0BENTEDBgBIhMI36n87pCIkgMV3UQ4BR3aSBpm"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CPM | 2026-01-13T08:48:25 |
https://socket.io/docs/v4/server-api/#namespace | Server API | Socket.IO Skip to main content Latest blog post (July 25, 2024): npm package provenance . Socket.IO Docs Guide Tutorial Examples Emit cheatsheet Server API Client API Ecosystem Help Troubleshooting Stack Overflow GitHub Discussions Slack News Blog Twitter Tools CDN Admin UI About FAQ Changelog Roadmap Become a sponsor 4.x 4.x 3.x 2.x Changelog English English Español Français Português (Brasil) 中文（中国） Search Socket.IO API Options API Version: 4.x On this page Server API Server Related documentation pages: installation initialization details of the server instance Constructor new Server(httpServer [, options] ) httpServer <http.Server> | <https.Server> options <Object> import { createServer } from "http" ; import { Server } from "socket.io" ; const httpServer = createServer ( ) ; const io = new Server ( httpServer , { // options } ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; httpServer . listen ( 3000 ) ; The complete list of available options can be found here . new Server(port [, options] ) port <number> options <Object> import { Server } from "socket.io" ; const io = new Server ( 3000 , { // options } ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; The complete list of available options can be found here . new Server(options) options <Object> import { Server } from "socket.io" ; const io = new Server ( { // options } ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; io . listen ( 3000 ) ; The complete list of available options can be found here . Events Event: 'connect' Synonym of Event: "connection" . Event: 'connection' socket (Socket) socket connection with client Fired upon a connection from client. io . on ( "connection" , ( socket ) => { // ... } ) ; Event: 'new_namespace' namespace Namespace Fired when a new namespace is created: io . on ( "new_namespace" , ( namespace ) => { // ... } ) ; This can be useful for example: to attach a shared middleware to each namespace io . on ( "new_namespace" , ( namespace ) => { namespace . use ( myMiddleware ) ; } ) ; to track the dynamically created namespaces io . of ( / \/nsp-\w+ / ) ; io . on ( "new_namespace" , ( namespace ) => { console . log ( namespace . name ) ; } ) ; Attributes server.engine A reference to the underlying Engine.IO server. See here . server.sockets <Namespace> An alias for the main namespace ( / ). io . sockets . emit ( "hi" , "everyone" ) ; // is equivalent to io . of ( "/" ) . emit ( "hi" , "everyone" ) ; Methods server.adapter( [value] ) value <Adapter> Returns <Server> | <Adapter> Sets the adapter value . Defaults to an instance of the Adapter that ships with socket.io which is memory based. See socket.io-adapter . If no arguments are supplied this method returns the current value. import { Server } from "socket.io" ; import { createAdapter } from "@socket.io/redis-adapter" ; import { createClient } from "redis" ; const io = new Server ( ) ; const pubClient = createClient ( { host : "localhost" , port : 6379 } ) ; const subClient = pubClient . duplicate ( ) ; io . adapter ( createAdapter ( pubClient , subClient ) ) ; // redis@3 io . listen ( 3000 ) ; // redis@4 Promise . all ( [ pubClient . connect ( ) , subClient . connect ( ) ] ) . then ( ( ) => { io . listen ( 3000 ) ; } ) ; server.attach(httpServer [, options] ) httpServer <http.Server> | <https.Server> options <Object> Attaches the Server to an httpServer with the supplied options . import { createServer } from "http" ; import { Server } from "socket.io" ; const httpServer = createServer ( ) ; const io = new Server ( ) ; io . attach ( httpServer ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; httpServer . listen ( 3000 ) ; server.attach(port [, options] ) port <number> options <Object> Attaches the Server on the given port with the supplied options . import { Server } from "socket.io" ; const io = new Server ( ) ; io . attach ( 3000 ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; server.attachApp(app [, options] ) app <uws.App> options <Object> Attaches the Socket.IO server to an µWebSockets.js app: import { App } from "uWebSockets.js" ; import { Server } from "socket.io" ; const app = App ( ) ; const io = new Server ( ) ; io . attachApp ( app ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; app . listen ( 3000 , ( token ) => { if ( ! token ) { console . warn ( "port already in use" ) ; } } ) ; server.bind(engine) engine <engine.Server> Returns <Server> Advanced use only. Binds the server to a specific engine.io Server (or compatible API) instance. import { createServer } from "node:http" ; import { Server as Engine } from "engine.io" ; import { Server } from "socket.io" ; const httpServer = createServer ( ( req , res ) => { res . writeHead ( 404 ) . end ( ) ; } ) ; const engine = new Engine ( ) ; engine . attach ( httpServer , { path : "/socket.io/" } ) ; const io = new Server ( ) ; io . bind ( engine ) ; httpServer . listen ( 3000 ) ; server.close( [callback] ) callback <Function> Closes the Socket.IO server and disconnect all clients. The callback argument is optional and will be called when all connections are closed. info This also closes the underlying HTTP server. import { createServer } from "http" ; import { Server } from "socket.io" ; const PORT = 3030 ; const io = new Server ( PORT ) ; io . close ( ) ; const httpServer = createServer ( ) ; httpServer . listen ( PORT ) ; // PORT is free to use io . attach ( httpServer ) ; note Only closing the underlying HTTP server is not sufficient, as it will only prevent the server from accepting new connections but clients connected with WebSocket will not be disconnected right away. Reference: https://nodejs.org/api/http.html#serverclosecallback server.disconnectSockets( [close] ) Added in v4.0.0 Alias for io.of("/").disconnectSockets(close) . // make all Socket instances disconnect io . disconnectSockets ( ) ; // make all Socket instances in the "room1" room disconnect (and close the low-level connection) io . in ( "room1" ) . disconnectSockets ( true ) ; tip This method also works within a cluster of multiple Socket.IO servers, with a compatible adapter like the Postgres adapter . In that case, if you only want to affect the socket instances on the given node, you need to use the local flag: // make all Socket instances that are currently connected on the given node disconnect io . local . disconnectSockets ( ) ; See here . server.emit(eventName [, ...args] ) History Version Changes v4.5.0 io.emit() now supports acknowledgements. v1.0.0 Initial implementation. eventName <string> | <symbol> args any[] Returns true Emits an event to all connected clients in the main namespace. io . emit ( "hello" ) ; Any number of parameters can be included, and all serializable data structures are supported: io . emit ( "hello" , 1 , "2" , { "3" : 4 } , Buffer . from ( [ 5 ] ) ) ; And on the receiving side: socket . on ( "hello" , ( arg1 , arg2 , arg3 , arg4 ) => { console . log ( arg1 ) ; // 1 console . log ( arg2 ) ; // "2" console . log ( arg3 ) ; // { "3": 4 } console . log ( arg4 ) ; // ArrayBuffer or Buffer, depending on the platform } ) ; info The arguments will automatically be serialized, so calling JSON.stringify() is not needed. You can use to() and except() to send the packet to specific clients: // the “hello” event will be broadcast to all connected clients that are either // in the "room1" room or in the "room2" room, excluding those in the "room3" room io . to ( "room1" ) . to ( "room2" ) . except ( "room3" ) . emit ( "hello" ) ; Starting with version 4.5.0 , it is now possible to use acknowledgements when broadcasting: io . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; caution Calling timeout() is mandatory in that case. server.emitWithAck(eventName [, ...args] ) Added in v4.6.0 eventName <string> | <symbol> args any[] Returns Promise<any[]> Promised-based version of broadcasting and expecting an acknowledgement from all targeted clients: try { const responses = await io . timeout ( 10000 ) . emitWithAck ( "some-event" ) ; console . log ( responses ) ; // one response per client } catch ( e ) { // some clients did not acknowledge the event in the given delay } The example above is equivalent to: io . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; And on the receiving side: socket . on ( "some-event" , ( callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; server.except(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have not joined the given rooms . // the "foo" event will be broadcast to all connected clients, except the ones that are in the "room-101" room io . except ( "room-101" ) . emit ( "foo" , "bar" ) ; // with an array of rooms io . except ( [ "room-101" , "room-102" ] ) . emit ( "foo" , "bar" ) ; // with multiple chained calls io . except ( "room-101" ) . except ( "room-102" ) . emit ( "foo" , "bar" ) ; server.fetchSockets() Added in v4.0.0 Alias for io.of("/").fetchSocket() . // return all Socket instances of the main namespace const sockets = await io . fetchSockets ( ) ; // return all Socket instances in the "room1" room of the main namespace const sockets = await io . in ( "room1" ) . fetchSockets ( ) ; Sample usage: io . on ( "connection" , ( socket ) => { const userId = computeUserId ( socket ) ; socket . join ( userId ) ; socket . on ( "disconnect" , async ( ) => { const sockets = await io . in ( userId ) . fetchSockets ( ) ; if ( sockets . length === 0 ) { // no more active connections for the given user } } ) ; } ) ; tip This method also works within a cluster of multiple Socket.IO servers, with a compatible adapter like the Postgres adapter . In that case, if you only want to return the socket instances on the given node, you need to use the local flag: // return all Socket instances that are currently connected on the given node const sockets = await io . local . fetchSockets ( ) ; See here . server.in(room) Added in v1.0.0 Synonym of server.to(room) , but might feel clearer in some cases: // disconnect all clients in the "room-101" room io . in ( "room-101" ) . disconnectSockets ( ) ; server.listen(httpServer [, options] ) Synonym of server.attach(httpServer[, options]) . server.listen(port [, options] ) Synonym of server.attach(port[, options]) . server.of(nsp) nsp <string> | <RegExp> | <Function> Returns <Namespace> Initializes and retrieves the given Namespace by its pathname identifier nsp . If the namespace was already initialized it returns it immediately. const adminNamespace = io . of ( "/admin" ) ; A regex or a function can also be provided, in order to create namespace in a dynamic way: const dynamicNsp = io . of ( / ^\/dynamic-\d+$ / ) . on ( "connection" , ( socket ) => { const newNamespace = socket . nsp ; // newNamespace.name === "/dynamic-101" // broadcast to all clients in the given sub-namespace newNamespace . emit ( "hello" ) ; } ) ; // client-side const socket = io ( "/dynamic-101" ) ; // broadcast to all clients in each sub-namespace dynamicNsp . emit ( "hello" ) ; // use a middleware for each sub-namespace dynamicNsp . use ( ( socket , next ) => { /* ... */ } ) ; With a function: io . of ( ( name , query , next ) => { // the checkToken method must return a boolean, indicating whether the client is able to connect or not. next ( null , checkToken ( query . token ) ) ; } ) . on ( "connection" , ( socket ) => { /* ... */ } ) ; server.on(eventName, listener) Inherited from the EventEmitter class . eventName <string> | <symbol> listener <Function> Returns <Server> Adds the listener function to the end of the listeners array for the event named eventName . Available events: connection new_namespace any custom event from the serverSideEmit method io . on ( "connection" , ( socket ) => { // ... } ) ; server.onconnection(socket) socket <engine.Socket> Returns <Server> Advanced use only. Creates a new socket.io client from the incoming engine.io (or compatible API) Socket . import { Server } from "socket.io" ; import { Server as Engine } from "engine.io" ; const engine = new Engine ( ) ; const io = new Server ( ) ; engine . on ( "connection" , ( socket ) => { io . onconnection ( socket ) ; } ) ; engine . listen ( 3000 ) ; server.path( [value] ) value <string> Returns <Server> | <string> Sets the path value under which engine.io and the static files will be served. Defaults to /socket.io/ . If no arguments are supplied this method returns the current value. import { Server } from "socket.io" ; const io = new Server ( ) ; io . path ( "/myownpath/" ) ; danger The path value must match the one on the client side: import { io } from "socket.io-client" ; const socket = io ( { path : "/myownpath/" } ) ; server.serveClient( [value] ) value <boolean> Returns <Server> | <boolean> If value is true the attached server will serve the client files. Defaults to true . This method has no effect after listen is called. If no arguments are supplied this method returns the current value. import { Server } from "socket.io" ; const io = new Server ( ) ; io . serveClient ( false ) ; io . listen ( 3000 ) ; server.serverSideEmit(eventName [, ...args][, ack] ) Added in v4.1.0 Alias for: io.of("/").serverSideEmit(/* ... */); eventName <string> args <any[]> ack <Function> Returns true Sends a message to the other Socket.IO servers of the cluster . Syntax: io . serverSideEmit ( "hello" , "world" ) ; And on the receiving side: io . on ( "hello" , ( arg1 ) => { console . log ( arg1 ) ; // prints "world" } ) ; Acknowledgements are supported too: // server A io . serverSideEmit ( "ping" , ( err , responses ) => { console . log ( responses [ 0 ] ) ; // prints "pong" } ) ; // server B io . on ( "ping" , ( cb ) => { cb ( "pong" ) ; } ) ; Notes: the connection , connect and new_namespace strings are reserved and cannot be used in your application. you can send any number of arguments, but binary structures are currently not supported (the array of arguments will be JSON.stringify -ed) Example: io . serverSideEmit ( "hello" , "world" , 1 , "2" , { 3 : "4" } ) ; the acknowledgement callback might be called with an error, if the other Socket.IO servers do not respond after a given delay io . serverSideEmit ( "ping" , ( err , responses ) => { if ( err ) { // at least one Socket.IO server has not responded // the 'responses' array contains all the responses already received though } else { // success! the 'responses' array contains one object per other Socket.IO server in the cluster } } ) ; server.serverSideEmitWithAck(eventName [, ...args] ) Added in v4.6.0 Alias for: io.of("/").serverSideEmitWithAck(/* ... */); eventName <string> args <any[]> ack <Function> Returns Promise<any[]> Promised-based version of broadcasting and expecting an acknowledgement from the other Socket.IO servers of the cluster . try { const responses = await io . serverSideEmitWithAck ( "some-event" ) ; console . log ( responses ) ; // one response per server (except itself) } catch ( e ) { // some servers did not acknowledge the event in the given delay } The example above is equivalent to: io . serverSideEmit ( "some-event" , ( err , responses ) => { if ( err ) { // some servers did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per server (except itself) } } ) ; And on the receiving side: io . on ( "some-event" , ( callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; server.socketsJoin(rooms) Added in v4.0.0 Alias for io.of("/").socketsJoin(rooms) . // make all Socket instances join the "room1" room io . socketsJoin ( "room1" ) ; // make all Socket instances in the "room1" room join the "room2" and "room3" rooms io . in ( "room1" ) . socketsJoin ( [ "room2" , "room3" ] ) ; // this also works with a single socket ID io . in ( theSocketId ) . socketsJoin ( "room1" ) ; tip This method also works within a cluster of multiple Socket.IO servers, with a compatible adapter like the Postgres adapter . In that case, if you only want to affect the socket instances on the given node, you need to use the local flag: // make all Socket instances that are currently connected on the given node join the "room1" room io . local . socketsJoin ( "room1" ) ; See here . server.socketsLeave(rooms) Added in v4.0.0 Alias for io.of("/").socketsLeave(rooms) . // make all Socket instances leave the "room1" room io . socketsLeave ( "room1" ) ; // make all Socket instances in the "room1" room leave the "room2" and "room3" rooms io . in ( "room1" ) . socketsLeave ( [ "room2" , "room3" ] ) ; // this also works with a single socket ID io . in ( theSocketId ) . socketsLeave ( "room1" ) ; tip This method also works within a cluster of multiple Socket.IO servers, with a compatible adapter like the Postgres adapter . In that case, if you only want to affect the socket instances on the given node, you need to use the local flag: // make all Socket instances that are currently connected on the given node leave the "room1" room io . local . socketsLeave ( "room1" ) ; See here . server.timeout(value) Added in v4.5.0 value <number> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the callback will be called with an error when the given number of milliseconds have elapsed without an acknowledgement from all targeted clients: io . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; server.to(room) History Version Changes v4.0.0 Allow to pass an array of rooms. v1.0.0 Initial implementation. room <string> | <string[]> Returns BroadcastOperator for chaining Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have joined the given room . To emit to multiple rooms, you can call to several times. // the “foo” event will be broadcast to all connected clients in the “room-101” room io . to ( "room-101" ) . emit ( "foo" , "bar" ) ; // with an array of rooms (a client will be notified at most once) io . to ( [ "room-101" , "room-102" ] ) . emit ( "foo" , "bar" ) ; // with multiple chained calls io . to ( "room-101" ) . to ( "room-102" ) . emit ( "foo" , "bar" ) ; server.use(fn) Added in v1.0.0 Alias for io.of("/").use(fn) . fn <Function> Registers a middleware for the main namespace, which is a function that gets executed for every incoming Socket , and receives as parameters the socket and a function to optionally defer execution to the next registered middleware. Errors passed to middleware callbacks are sent as special connect_error packets to clients. Server io . use ( ( socket , next ) => { const err = new Error ( "not authorized" ) ; err . data = { content : "Please retry later" } ; // additional details next ( err ) ; } ) ; Client socket . on ( "connect_error" , err => { console . log ( err instanceof Error ) ; // true console . log ( err . message ) ; // not authorized console . log ( err . data ) ; // { content: "Please retry later" } } ) ; More information can be found here . info If you are looking for Express middlewares, please check this section . Namespace Represents a pool of sockets connected under a given scope identified by a pathname (eg: /chat ). More information can be found here . Attributes namespace.adapter <Adapter> The "Adapter" used for the namespace. Note: the adapter of the main namespace can be accessed with io.of("/").adapter . More information about it here . const adapter = io . of ( "/my-namespace" ) . adapter ; namespace.name <string> The namespace identifier property. namespace.sockets Map<SocketId, Socket> A map of Socket instances that are connected to this namespace. // number of sockets in this namespace (on this node) const socketCount = io . of ( "/admin" ) . sockets . size ; Events Event: 'connect' Synonym of Event: "connection" . Event: 'connection' socket <Socket> Fired upon a connection from client. // main namespace io . on ( "connection" , ( socket ) => { // ... } ) ; // custom namespace io . of ( "/admin" ) . on ( "connection" , ( socket ) => { // ... } ) ; Methods namespace.allSockets() Returns Promise<Set<SocketId>> caution This method will be removed in the next major release, please use serverSideEmit() or fetchSockets() instead. Gets a list of socket IDs connected to this namespace (across all nodes if applicable). // all sockets in the main namespace const ids = await io . allSockets ( ) ; // all sockets in the main namespace and in the "user:1234" room const ids = await io . in ( "user:1234" ) . allSockets ( ) ; // all sockets in the "chat" namespace const ids = await io . of ( "/chat" ) . allSockets ( ) ; // all sockets in the "chat" namespace and in the "general" room const ids = await io . of ( "/chat" ) . in ( "general" ) . allSockets ( ) ; namespace.disconnectSockets( [close] ) Added in v4.0.0 close <boolean> whether to close the underlying connection Returns void Makes the matching Socket instances disconnect. // make all Socket instances disconnect io . disconnectSockets ( ) ; // make all Socket instances in the "room1" room disconnect (and discard the low-level connection) io . in ( "room1" ) . disconnectSockets ( true ) ; // make all Socket instances in the "room1" room of the "admin" namespace disconnect io . of ( "/admin" ) . in ( "room1" ) . disconnectSockets ( ) ; // this also works with a single socket ID io . of ( "/admin" ) . in ( theSocketId ) . disconnectSockets ( ) ; namespace.emit(eventName [, ...args] ) History Version Changes v4.5.0 io.emit() now supports acknowledgements. v1.0.0 Initial implementation. eventName <string> | <symbol> args any[] Returns true Emits an event to all connected clients in the given namespace. io . of ( "/chat" ) . emit ( "hello" ) ; Any number of parameters can be included, and all serializable data structures are supported: io . of ( "/chat" ) . emit ( "hello" , 1 , "2" , { "3" : 4 } , Buffer . from ( [ 5 ] ) ) ; And on the receiving side: socket . on ( "hello" , ( arg1 , arg2 , arg3 , arg4 ) => { console . log ( arg1 ) ; // 1 console . log ( arg2 ) ; // "2" console . log ( arg3 ) ; // { "3": 4 } console . log ( arg4 ) ; // ArrayBuffer or Buffer, depending on the platform } ) ; info The arguments will automatically be serialized, so calling JSON.stringify() is not needed. You can use to() and except() to send the packet to specific clients: // the “hello” event will be broadcast to all connected clients that are either // in the "room1" room or in the "room2" room, excluding those in the "room3" room io . of ( "/chat" ) . to ( "room1" ) . to ( "room2" ) . except ( "room3" ) . emit ( "hello" ) ; Starting with version 4.5.0 , it is now possible to use acknowledgements when broadcasting: io . of ( "/chat" ) . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; caution Calling timeout() is mandatory in that case. namespace.emitWithAck(eventName [, ...args] ) Added in v4.6.0 eventName <string> | <symbol> args any[] Returns Promise<any[]> Promised-based version of broadcasting and expecting an acknowledgement from all targeted clients in the given namespace: try { const responses = await io . of ( "/chat" ) . timeout ( 10000 ) . emitWithAck ( "some-event" ) ; console . log ( responses ) ; // one response per client } catch ( e ) { // some clients did not acknowledge the event in the given delay } The example above is equivalent to: io . of ( "/chat" ) . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; And on the receiving side: socket . on ( "some-event" , ( callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; namespace.except(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have not joined the given rooms . const myNamespace = io . of ( "/my-namespace" ) ; // the "foo" event will be broadcast to all connected clients, except the ones that are in the "room-101" room myNamespace . except ( "room-101" ) . emit ( "foo" , "bar" ) ; // with an array of rooms myNamespace . except ( [ "room-101" , "room-102" ] ) . emit ( "foo" , "bar" ) ; // with multiple chained calls myNamespace . except ( "room-101" ) . except ( "room-102" ) . emit ( "foo" , "bar" ) ; namespace.fetchSockets() Added in v4.0.0 Returns Socket[] | RemoteSocket[] Returns the matching Socket instances: // return all Socket instances in the main namespace const sockets = await io . fetchSockets ( ) ; // return all Socket instances in the "room1" room of the main namespace const sockets = await io . in ( "room1" ) . fetchSockets ( ) ; // return all Socket instances in the "room1" room of the "admin" namespace const sockets = await io . of ( "/admin" ) . in ( "room1" ) . fetchSockets ( ) ; // this also works with a single socket ID const sockets = await io . in ( theSocketId ) . fetchSockets ( ) ; The sockets variable in the example above is an array of objects exposing a subset of the usual Socket class: for ( const socket of sockets ) { console . log ( socket . id ) ; console . log ( socket . handshake ) ; console . log ( socket . rooms ) ; console . log ( socket . data ) ; socket . emit ( /* ... */ ) ; socket . join ( /* ... */ ) ; socket . leave ( /* ... */ ) ; socket . disconnect ( /* ... */ ) ; } The data attribute is an arbitrary object that can be used to share information between Socket.IO servers: // server A io . on ( "connection" , ( socket ) => { socket . data . username = "alice" ; } ) ; // server B const sockets = await io . fetchSockets ( ) ; console . log ( sockets [ 0 ] . data . username ) ; // "alice" Important note : this method (and socketsJoin , socketsLeave and disconnectSockets too) is compatible with the Redis adapter (starting with socket.io-redis@6.1.0 ), which means that they will work across Socket.IO servers. namespace.in(room) Added in v1.0.0 Synonym of namespace.to(room) , but might feel clearer in some cases: const myNamespace = io . of ( "/my-namespace" ) ; // disconnect all clients in the "room-101" room myNamespace . in ( "room-101" ) . disconnectSockets ( ) ; namespace.serverSideEmit(eventName [, ...args][, ack] ) Added in v4.1.0 eventName <string> args <any[]> ack <Function> Returns true Sends a message to the other Socket.IO servers of the cluster . Syntax: io . of ( "/chat" ) . serverSideEmit ( "hello" , "world" ) ; And on the receiving side: io . of ( "/chat" ) . on ( "hello" , ( arg1 ) => { console . log ( arg1 ) ; // prints "world" } ) ; Acknowledgements are supported too: // server A io . of ( "/chat" ) . serverSideEmit ( "ping" , ( err , responses ) => { console . log ( responses [ 0 ] ) ; // prints "pong" } ) ; // server B io . of ( "/chat" ) . on ( "ping" , ( cb ) => { cb ( "pong" ) ; } ) ; Notes: the connection , connect and new_namespace strings are reserved and cannot be used in your application. you can send any number of arguments, but binary structures are currently not supported (the array of arguments will be JSON.stringify -ed) Example: io . of ( "/chat" ) . serverSideEmit ( "hello" , "world" , 1 , "2" , { 3 : "4" } ) ; the acknowledgement callback might be called with an error, if the other Socket.IO servers do not respond after a given delay io . of ( "/chat" ) . serverSideEmit ( "ping" , ( err , responses ) => { if ( err ) { // at least one Socket.IO server has not responded // the 'responses' array contains all the responses already received though } else { // success! the 'responses' array contains one object per other Socket.IO server in the cluster } } ) ; namespace.serverSideEmitWithAck(eventName [, ...args] ) Added in v4.6.0 eventName <string> args <any[]> ack <Function> Returns Promise<any[]> Promised-based version of broadcasting and expecting an acknowledgement from the other Socket.IO servers of the cluster . try { const responses = await io . of ( "/chat" ) . serverSideEmitWithAck ( "some-event" ) ; console . log ( responses ) ; // one response per server (except itself) } catch ( e ) { // some servers did not acknowledge the event in the given delay } The example above is equivalent to: io . of ( "/chat" ) . serverSideEmit ( "some-event" , ( err , responses ) => { if ( err ) { // some servers did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per server (except itself) } } ) ; And on the receiving side: io . of ( "/chat" ) . on ( "some-event" , ( callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; namespace.socketsJoin(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns void Makes the matching Socket instances join the specified rooms: // make all Socket instances join the "room1" room io . socketsJoin ( "room1" ) ; // make all Socket instances in the "room1" room join the "room2" and "room3" rooms io . in ( "room1" ) . socketsJoin ( [ "room2" , "room3" ] ) ; // make all Socket instances in the "room1" room of the "admin" namespace join the "room2" room io . of ( "/admin" ) . in ( "room1" ) . socketsJoin ( "room2" ) ; // this also works with a single socket ID io . in ( theSocketId ) . socketsJoin ( "room1" ) ; More information can be found here . namespace.socketsLeave(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns void Makes the matching Socket instances leave the specified rooms: // make all Socket instances leave the "room1" room io . socketsLeave ( "room1" ) ; // make all Socket instances in the "room1" room leave the "room2" and "room3" rooms io . in ( "room1" ) . socketsLeave ( [ "room2" , "room3" ] ) ; // make all Socket instances in the "room1" room of the "admin" namespace leave the "room2" room io . of ( "/admin" ) . in ( "room1" ) . socketsLeave ( "room2" ) ; // this also works with a single socket ID io . in ( theSocketId ) . socketsLeave ( "room1" ) ; namespace.timeout(value) Added in v4.5.0 value <number> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the callback will be called with an error when the given number of milliseconds have elapsed without an acknowledgement from the client: io . of ( "/chat" ) . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; namespace.to(room) History Version Changes v4.0.0 Allow to pass an array of rooms. v1.0.0 Initial implementation. room <string> | <string[]> Returns BroadcastOperator for chaining Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have joined the given room . To emit to multiple rooms, you can call to several times. const myNamespace = io . of ( "/my-namespace" ) ; // the “foo” event will be broadcast to all connected clients in the “room-101” room myNamespace . to ( "room-101" ) . emit ( "foo" , "bar" ) ; // with an array of rooms (a client will be notified at most once) myNamespace . to ( [ "room-101" , "room-102" ] ) . emit ( "foo" , "bar" ) ; // with multiple chained calls myNamespace . to ( "room-101" ) . to ( "room-102" ) . emit ( "foo" , "bar" ) ; namespace.use(fn) Added in v1.0.0 fn <Function> Registers a middleware for the given namespace, which is a function that gets executed for every incoming Socket , and receives as parameters the socket and a function to optionally defer execution to the next registered middleware. Errors passed to middleware callbacks are sent as special connect_error packets to clients. Server io . of ( "/chat" ) . use ( ( socket , next ) => { const err = new Error ( "not authorized" ) ; err . data = { content : "Please retry later" } ; // additional details next ( err ) ; } ) ; Client socket . on ( "connect_error" , err => { console . log ( err instanceof Error ) ; // true console . log ( err . message ) ; // not authorized console . log ( err . data ) ; // { content: "Please retry later" } } ) ; More information can be found here . info If you are looking for Express middlewares, please check this section . Flags Flag: 'local' Sets a modifier for a subsequent event emission that the event data will only be broadcast to the current node (when scaling to multiple nodes ). io . local . emit ( "an event" , { some : "data" } ) ; Flag: 'volatile' Sets a modifier for a subsequent event emission that the event data may be lost if the clients are not ready to receive messages (because of network slowness or other issues, or because they’re connected through long polling and is in the middle of a request-response cycle). io . volatile . emit ( "an event" , { some : "data" } ) ; // the clients may or may not receive it Socket A Socket is the fundamental class for interacting with browser clients. A Socket belongs to a certain Namespace (by default / ) and uses an underlying Client to communicate. It should be noted the Socket doesn't relate directly to the actual underlying TCP/IP socket and it is only the name of the class. Within each Namespace , you can also define arbitrary channels (called room ) that the Socket can join and leave. That provides a convenient way to broadcast to a group of Socket s (see Socket#to below). The Socket class inherits from EventEmitter . The Socket class overrides the emit method, and does not modify any other EventEmitter method. All methods documented here which also appear as EventEmitter methods (apart from emit ) are implemented by EventEmitter , and documentation for EventEmitter applies. More information can be found here . Events Event: 'disconnect' reason <string> the reason of the disconnection (either client or server-side) Fired upon disconnection. io . on ( "connection" , ( socket ) => { socket . on ( "disconnect" , ( reason ) => { // ... } ) ; } ) ; Possible reasons: Reason Description server namespace disconnect The socket was forcefully disconnected with socket.disconnect() . client namespace disconnect The client has manually disconnected the socket using socket.disconnect() . server shutting down The server is, well, shutting down. ping timeout The client did not send a PONG packet in the pingTimeout delay. transport close The connection was closed (example: the user has lost connection, or the network was changed from WiFi to 4G). transport error The connection has encountered an error. parse error The server has received an invalid packet from the client. forced close The server has received an invalid packet from the client. forced server close The client did not join a namespace in time (see the connectTimeout option) and was forcefully closed. Event: 'disconnecting' Added in v1.5.0 reason <string> the reason of the disconnection (either client or server-side) Fired when the client is going to be disconnected (but hasn't left its rooms yet). io . on ( "connection" , ( socket ) => { socket . on ( "disconnecting" , ( reason ) => { console . log ( socket . rooms ) ; // Set { ... } } ) ; } ) ; With an asynchronous handler, you will need to create a copy of the rooms attribute: io . on ( "connection" , ( socket ) => { socket . on ( "disconnecting" , async ( reason ) => { const rooms = new Set ( socket . rooms ) ; await someLongRunningOperation ( ) ; // socket.rooms will be empty there console . log ( rooms ) ; } ) ; } ) ; caution Those events, along with connect , connect_error , newListener and removeListener , are special events that shouldn't be used in your application: // BAD, will throw an error socket . emit ( "disconnect" ) ; Attributes socket.client <Client> A reference to the underlying Client object. socket.conn <engine.Socket> A reference to the underlying Client transport connection (engine.io Socket object). This allows access to the IO transport layer, which still (mostly) abstracts the actual TCP/IP socket. io . on ( "connection" , ( socket ) => { console . log ( "initial transport" , socket . conn . transport . name ) ; // prints "polling" socket . conn . once ( "upgrade" , ( ) => { // called when the transport is upgraded (i.e. from HTTP long-polling to WebSocket) console . log ( "upgraded transport" , socket . conn . transport . name ) ; // prints "websocket" } ) ; socket . conn . on ( "packet" , ( { type , data } ) => { // called for each packet received } ) ; socket . conn . on ( "packetCreate" , ( { type , data } ) => { // called for each packet sent } ) ; socket . conn . on ( "drain" , ( ) => { // called when the write buffer is drained } ) ; socket . conn . on ( "heartbeat" , ( ) => { // called after each round trip of the heartbeat mechanism console . log ( "heartbeat" ) ; } ) ; socket . conn . on ( "close" , ( reason ) => { // called when the underlying connection is closed } ) ; } ) ; socket.data Added in v4.0.0 An arbitrary object that can be used in conjunction with the fetchSockets() utility method: io . on ( "connection" , ( socket ) => { socket . data . username = "alice" ; } ) ; const sockets = await io . fetchSockets ( ) ; console . log ( sockets [ 0 ] . data . username ) ; // "alice" tip This also works within a Socket.IO cluster, with a compatible adapter like the Postgres adapter . socket.handshake <Object> The handshake details: Field Type Description headers IncomingHttpHeaders The headers sent as part of the handshake. time <string> The date of creation (as string). address <string> The ip address of the client. xdomain <boolean> Whether the connection is cross-domain. secure <boolean> Whether the connection is made over SSL. issued <number> The date of creation (as unix timestamp). url <string> The request URL string. query Record<string, string or string[]> The query parameters of the first request. auth Record<string, any> The authentication payload. See also here . Usage: io . use ( ( socket , next ) => { let handshake = socket . handshake ; // ... } ) ; io . on ( "connection" , ( socket ) => { let handshake = socket . handshake ; // ... } ) ; Example: const handshake = { headers : { "user-agent" : "node-XMLHttpRequest" , accept : "*/*" , host : "localhost:3000" , connection : "close" } , time : "Wed Jan 01 2020 01:00:00 GMT+0100 (Central European Standard Time)" , address : "::ffff:127.0.0.1" , xdomain : false , secure : false , issued : 1577836800000 , url : "/socket.io/?EIO=4&transport=polling&t=OPAfXv5&b64=1" , query : { EIO : "4" , transport : "polling" , t : "OPAfXv5" , b64 : "1" } , auth : { } } Note: the headers attribute refers to the headers of the first HTTP request of the session, and won't be updated by the subsequent HTTP requests. io . on ( "connection" , ( socket ) => { console . log ( socket . handshake . headers === socket . request . headers ) ; // prints "true" } ) ; socket.id <string> A unique identifier for the session, that comes from the underlying Client . caution The id attribute is an ephemeral ID that is not meant to be used in your application (or only for debugging purposes) because: this ID is regenerated after each reconnection (for example when the WebSocket connection is severed, or when the user refreshes the page) two different browser tabs will have two different IDs there is no message queue stored for a given ID on the server (i.e. if the client is disconnected, the messages sent from the server to this ID are lost) Please use a regular session ID instead (either sent in a cookie, or stored in the localStorage and sent in the auth payload). See also: Part II of our private message guide How to deal with cookies socket.recovered Added in v4.6.0 <boolean> Whether the connection state was successfully recovered during the last reconnection. io . on ( "connection" , ( socket ) => { if ( socket . recovered ) { // recovery was successful: socket.id, socket.rooms and socket.data were restored } else { // new or unrecoverable session } } ) ; More information about this feature here . socket.request <http.IncomingMessage> A getter proxy that returns the reference to the request that originated the underlying engine.io Client . Useful for accessing request headers such as Cookie or User-Agent . import { parse } from "cookie" ; io . on ( "connection" , ( socket ) => { const cookies = parse ( socket . request . headers . cookie || "" ) ; } ) ; Note: socket.request refers to the first HTTP request of the session, and won't be updated by the subsequent HTTP requests. io . on ( "connection" , ( socket ) => { console . log ( socket . request . headers === socket . handshake . headers ) ; // prints "true" } ) ; If you don't need this reference, you can discard it in order to reduce the memory footprint: io . on ( "connection" , ( socket ) => { delete socket . conn . request ; } ) ; socket.rooms Set<string> A Set of strings identifying the rooms this client is in. io . on ( "connection" , ( socket ) => { console . log ( socket . rooms ) ; // Set { <socket.id> } socket . join ( "room1" ) ; console . log ( socket . rooms ) ; // Set { <socket.id>, "room1" } } ) ; Methods socket.compress(value) value <boolean> whether to following packet will be compressed Returns Socket for chaining Sets a modifier for a subsequent event emission that the event data will only be compressed if the value is true . Defaults to true when you don't call the method. io . on ( "connection" , ( socket ) => { socket . compress ( false ) . emit ( "uncompressed" , "that's rough" ) ; } ) ; socket.disconnect( [close] ) close <boolean> whether to close the underlying connection Returns Socket Disconnects this socket. If value of close is true , closes the underlying connection. Otherwise, it just disconnects the namespace. io . on ( "connection" , ( socket ) => { setTimeout ( ( ) => socket . disconnect ( true ) , 5000 ) ; } ) ; socket.emit(eventName [, ...args][, ack] ) (overrides EventEmitter.emit ) eventName <string> | <symbol> args <any[]> ack <Function> Returns true Emits an event to the socket identified by the string name. Any other parameters can be included. All serializable data structures are supported, including Buffer . io . on ( "connection" , ( ) => { socket . emit ( "hello" , "world" ) ; socket . emit ( "with-binary" , 1 , "2" , { 3 : "4" , 5 : Buffer . from ( [ 6 ] ) } ) ; } ) ; The ack argument is optional and will be called with the client's answer. Server io . on ( "connection" , ( socket ) => { socket . emit ( "hello" , "world" , ( response ) => { console . log ( response ) ; // "got it" } ) ; } ) ; Client socket . on ( "hello" , ( arg , callback ) => { console . log ( arg ) ; // "world" callback ( "got it" ) ; } ) ; socket.emitWithAck(eventName [, ...args] ) Added in v4.6.0 eventName <string> | <symbol> args any[] Returns Promise<any> Promised-based version of emitting and expecting an acknowledgement from the given client: io . on ( "connection" , async ( socket ) => { // without timeout const response = await socket . emitWithAck ( "hello" , "world" ) ; // with a specific timeout try { const response = await socket . timeout ( 10000 ) . emitWithAck ( "hello" , "world" ) ; } catch ( err ) { // the client did not acknowledge the event in the given delay } } ) ; The example above is equivalent to: io . on ( "connection" , ( socket ) => { // without timeout socket . emit ( "hello" , "world" , ( val ) => { // ... } ) ; // with a specific timeout socket . timeout ( 10000 ) . emit ( "hello" , "world" , ( err , val ) => { // ... } ) ; } ) ; And on the receiving side: socket . on ( "hello" , ( arg1 , callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; socket.eventNames() Inherited from EventEmitter (along with other methods not mentioned here). See the Node.js documentation for the events module. socket.except(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have not joined the given rooms (the socket itself being excluded). // to al | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements | Statements and declarations - JavaScript | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web JavaScript Reference Statements and declarations Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) Statements and declarations JavaScript applications consist of statements with an appropriate syntax. A single statement may span multiple lines. Multiple statements may occur on a single line if each statement is separated by a semicolon. This isn't a keyword, but a group of keywords. In this article Statements and declarations by category Difference between statements and declarations Browser compatibility See also Statements and declarations by category For an alphabetical listing see the sidebar on the left. Control flow return Specifies the value to be returned by a function. break Terminates the current loop, switch, or label statement and transfers program control to the statement following the terminated statement. continue Terminates execution of the statements in the current iteration of the current or labeled loop, and continues execution of the loop with the next iteration. throw Throws a user-defined exception. if...else Executes a statement if a specified condition is true. If the condition is false, another statement can be executed. switch Evaluates an expression, matching the expression's value to a case clause, and executes statements associated with that case. try...catch Marks a block of statements to try, and specifies a response, should an exception be thrown. Declaring variables var Declares a variable, optionally initializing it to a value. let Declares a block scope local variable, optionally initializing it to a value. const Declares a read-only named constant. using Declares local variables that are synchronously disposed . await using Declares local variables that are asynchronously disposed . Functions and classes function Declares a function with the specified parameters. function* Generator Functions enable writing iterators more easily. async function Declares an async function with the specified parameters. async function* Asynchronous Generator Functions enable writing async iterators more easily. class Declares a class. Iterations do...while Creates a loop that executes a specified statement until the test condition evaluates to false. The condition is evaluated after executing the statement, resulting in the specified statement executing at least once. for Creates a loop that consists of three optional expressions, enclosed in parentheses and separated by semicolons, followed by a statement executed in the loop. for...in Iterates over the enumerable properties of an object, in arbitrary order. For each distinct property, statements can be executed. for...of Iterates over iterable objects (including arrays , array-like objects, iterators and generators ), invoking a custom iteration hook with statements to be executed for the value of each distinct property. for await...of Iterates over async iterable objects, array-like objects, iterators and generators , invoking a custom iteration hook with statements to be executed for the value of each distinct property. while Creates a loop that executes a specified statement as long as the test condition evaluates to true. The condition is evaluated before executing the statement. Others Empty An empty statement is used to provide no statement, although the JavaScript syntax would expect one. Block A block statement is used to group zero or more statements. The block is delimited by a pair of curly braces. Expression statement An expression statement evaluates an expression and discards its result. It allows the expression to perform side effects, such as executing a function or updating a variable. debugger Invokes any available debugging functionality. If no debugging functionality is available, this statement has no effect. export Used to export functions to make them available for imports in external modules, and other scripts. import Used to import functions exported from an external module, another script. label Provides a statement with an identifier that you can refer to using a break or continue statement. with Deprecated Extends the scope chain for a statement. Difference between statements and declarations In this section, we will be mixing two kinds of constructs: statements and declarations . They are two disjoint sets of grammars. The following are declarations: let const function function* async function async function* class export (Note: it can only appear at the top-level of a module ) import (Note: it can only appear at the top-level of a module ) Everything else in the list above is a statement. The terms "statement" and "declaration" have a precise meaning in the formal syntax of JavaScript that affects where they may be placed in code. For example, in most control-flow structures, the body only accepts statements — such as the two arms of an if...else : js if (condition) statement1; else statement2; If you use a declaration instead of a statement, it would be a SyntaxError . For example, a let declaration is not a statement, so you can't use it in its bare form as the body of an if statement. js if (condition) let i = 0; // SyntaxError: Lexical declaration cannot appear in a single-statement context On the other hand, var is a statement, so you can use it on its own as the if body. js if (condition) var i = 0; You can see declarations as " binding identifiers to values", and statements as "carrying out actions". The fact that var is a statement instead of a declaration is a special case, because it doesn't follow normal lexical scoping rules and may create side effects — in the form of creating global variables, mutating existing var -defined variables, and defining variables that are visible outside of its block (because var -defined variables aren't block-scoped). As another example, labels can only be attached to statements. js label: const a = 1; // SyntaxError: Lexical declaration cannot appear in a single-statement context Note: There's a legacy grammar that allows function declarations to have labels , but it's only standardized for compatibility with web reality. To get around this, you can wrap the declaration in braces — this makes it part of a block statement . js label: { const a = 1; } if (condition) { let i = 0; } Browser compatibility Enable JavaScript to view this browser compatibility table. See also Expressions and operators Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jul 29, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar JavaScript Tutorials and guides JavaScript Guide Introduction Grammar and types Control flow and error handling Loops and iteration Functions Expressions and operators Numbers and strings Representing dates & times Regular expressions Indexed collections Keyed collections Working with objects Using classes Using promises JavaScript typed arrays Iterators and generators Resource management Internationalization JavaScript modules Intermediate Language overview JavaScript data structures Equality comparisons and sameness Enumerability and ownership of properties Closures Advanced Inheritance and the prototype chain Meta programming Memory Management References Built-in objects AggregateError Array ArrayBuffer AsyncDisposableStack AsyncFunction AsyncGenerator AsyncGeneratorFunction AsyncIterator Atomics BigInt BigInt64Array BigUint64Array Boolean DataView Date decodeURI() decodeURIComponent() DisposableStack encodeURI() encodeURIComponent() Error escape() Deprecated eval() EvalError FinalizationRegistry Float16Array Float32Array Float64Array Function Generator GeneratorFunction globalThis Infinity Int8Array Int16Array Int32Array InternalError Non-standard Intl isFinite() isNaN() Iterator JSON Map Math NaN Number Object parseFloat() parseInt() Promise Proxy RangeError ReferenceError Reflect RegExp Set SharedArrayBuffer String SuppressedError Symbol SyntaxError Temporal TypedArray TypeError Uint8Array Uint8ClampedArray Uint16Array Uint32Array undefined unescape() Deprecated URIError WeakMap WeakRef WeakSet Expressions & operators Addition (+) Addition assignment (+=) Assignment (=) async function expression async function* expression await Bitwise AND (&) Bitwise AND assignment (&=) Bitwise NOT (~) Bitwise OR (|) Bitwise OR assignment (|=) Bitwise XOR (^) Bitwise XOR assignment (^=) class expression Comma operator (,) Conditional (ternary) operator Decrement (--) delete Destructuring Division (/) Division assignment (/=) Equality (==) Exponentiation (**) Exponentiation assignment (**=) function expression function* expression Greater than (>) Greater than or equal (>=) Grouping operator ( ) import.meta import.meta.resolve() import() in Increment (++) Inequality (!=) instanceof Left shift (<<) Left shift assignment (<<=) Less than (<) Less than or equal (<=) Logical AND (&&) Logical AND assignment (&&=) Logical NOT (!) Logical OR (||) Logical OR assignment (||=) Multiplication (*) Multiplication assignment (*=) new new.target null Nullish coalescing assignment (??=) Nullish coalescing operator (??) Object initializer Operator precedence Optional chaining (?.) Property accessors Remainder (%) Remainder assignment (%=) Right shift (>>) Right shift assignment (>>=) Spread syntax (...) Strict equality (===) Strict inequality (!==) Subtraction (-) Subtraction assignment (-=) super this typeof Unary negation (-) Unary plus (+) Unsigned right shift (>>>) Unsigned right shift assignment (>>>=) void operator yield yield* Statements & declarations async function async function* await using Block statement break class const continue debugger do...while Empty statement export Expression statement for for await...of for...in for...of function function* if...else import Import attributes Labeled statement let return switch throw try...catch using var while with Deprecated Functions Arrow function expressions Default parameters get Method definitions Rest parameters set The arguments object [Symbol.iterator]() callee Deprecated length Classes constructor extends Private elements Public class fields static Static initialization blocks Regular expressions Backreference: \1, \2 Capturing group: (...) Character class escape: \d, \D, \w, \W, \s, \S Character class: [...], [^...] Character escape: \n, \u{...} Disjunction: | Input boundary assertion: ^, $ Literal character: a, b Lookahead assertion: (?=...), (?!...) Lookbehind assertion: (?<=...), (?<!...) Modifier: (?ims-ims:...) Named backreference: \k<name> Named capturing group: (?<name>...) Non-capturing group: (?:...) Quantifier: *, +, ?, {n}, {n,}, {n,m} Unicode character class escape: \p{...}, \P{...} Wildcard: . Word boundary assertion: \b, \B Errors AggregateError: No Promise in Promise.any was resolved Error: Permission denied to access property "x" InternalError: too much recursion RangeError: argument is not a valid code point RangeError: BigInt division by zero RangeError: BigInt negative exponent RangeError: form must be one of 'NFC', 'NFD', 'NFKC', or 'NFKD' RangeError: invalid array length RangeError: invalid date RangeError: precision is out of range RangeError: radix must be an integer RangeError: repeat count must be less than infinity RangeError: repeat count must be non-negative RangeError: x can't be converted to BigInt because it isn't an integer ReferenceError: "x" is not defined ReferenceError: assignment to undeclared variable "x" ReferenceError: can't access lexical declaration 'X' before initialization ReferenceError: must call super constructor before using 'this' in derived class constructor ReferenceError: super() called twice in derived class constructor SyntaxError: 'arguments'/'eval' can't be defined or assigned to in strict mode code SyntaxError: "0"-prefixed octal literals are deprecated SyntaxError: "use strict" not allowed in function with non-simple parameters SyntaxError: "x" is a reserved identifier SyntaxError: \ at end of pattern SyntaxError: a declaration in the head of a for-of loop can't have an initializer SyntaxError: applying the 'delete' operator to an unqualified name is deprecated SyntaxError: arguments is not valid in fields SyntaxError: await is only valid in async functions, async generators and modules SyntaxError: await/yield expression can't be used in parameter SyntaxError: cannot use `??` unparenthesized within `||` and `&&` expressions SyntaxError: character class escape cannot be used in class range in regular expression SyntaxError: continue must be inside loop SyntaxError: duplicate capture group name in regular expression SyntaxError: duplicate formal argument x SyntaxError: for-in loop head declarations may not have initializers SyntaxError: function statement requires a name SyntaxError: functions cannot be labelled SyntaxError: getter and setter for private name #x should either be both static or non-static SyntaxError: getter functions must have no arguments SyntaxError: identifier starts immediately after numeric literal SyntaxError: illegal character SyntaxError: import declarations may only appear at top level of a module SyntaxError: incomplete quantifier in regular expression SyntaxError: invalid assignment left-hand side SyntaxError: invalid BigInt syntax SyntaxError: invalid capture group name in regular expression SyntaxError: invalid character in class in regular expression SyntaxError: invalid class set operation in regular expression SyntaxError: invalid decimal escape in regular expression SyntaxError: invalid identity escape in regular expression SyntaxError: invalid named capture reference in regular expression SyntaxError: invalid property name in regular expression SyntaxError: invalid range in character class SyntaxError: invalid regexp group SyntaxError: invalid regular expression flag "x" SyntaxError: invalid unicode escape in regular expression SyntaxError: JSON.parse: bad parsing SyntaxError: label not found SyntaxError: missing : after property id SyntaxError: missing ) after argument list SyntaxError: missing ) after condition SyntaxError: missing ] after element list SyntaxError: missing } after function body SyntaxError: missing } after property list SyntaxError: missing = in const declaration SyntaxError: missing formal parameter SyntaxError: missing name after . operator SyntaxError: missing variable name SyntaxError: negated character class with strings in regular expression SyntaxError: new keyword cannot be used with an optional chain SyntaxError: nothing to repeat SyntaxError: numbers out of order in {} quantifier. SyntaxError: octal escape sequences can't be used in untagged template literals or in strict mode code SyntaxError: parameter after rest parameter SyntaxError: private fields can't be deleted SyntaxError: property name __proto__ appears more than once in object literal SyntaxError: raw bracket is not allowed in regular expression with unicode flag SyntaxError: redeclaration of formal parameter "x" SyntaxError: reference to undeclared private field or method #x SyntaxError: rest parameter may not have a default SyntaxError: return not in function SyntaxError: setter functions must have one argument SyntaxError: string literal contains an unescaped line break SyntaxError: super() is only valid in derived class constructors SyntaxError: tagged template cannot be used with optional chain SyntaxError: Unexpected '#' used outside of class body SyntaxError: Unexpected token SyntaxError: unlabeled break must be inside loop or switch SyntaxError: unparenthesized unary expression can't appear on the left-hand side of '**' SyntaxError: use of super property/member accesses only valid within methods or eval code within methods SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed TypeError: 'x' is not iterable TypeError: "x" is (not) "y" TypeError: "x" is not a constructor TypeError: "x" is not a function TypeError: "x" is not a non-null object TypeError: "x" is read-only TypeError: already executing generator TypeError: BigInt value can't be serialized in JSON TypeError: calling a builtin X constructor without new is forbidden TypeError: can't access/set private field or method: object is not the right class TypeError: can't assign to property "x" on "y": not an object TypeError: can't convert BigInt to number TypeError: can't convert x to BigInt TypeError: can't define property "x": "obj" is not extensible TypeError: can't delete non-configurable array element TypeError: can't redefine non-configurable property "x" TypeError: can't set prototype of this object TypeError: can't set prototype: it would cause a prototype chain cycle TypeError: cannot use 'in' operator to search for 'x' in 'y' TypeError: class constructors must be invoked with 'new' TypeError: cyclic object value TypeError: derived class constructor returned invalid value x TypeError: getting private setter-only property TypeError: Initializing an object twice is an error with private fields/methods TypeError: invalid 'instanceof' operand 'x' TypeError: invalid Array.prototype.sort argument TypeError: invalid assignment to const "x" TypeError: Iterator/AsyncIterator constructor can't be used directly TypeError: matchAll/replaceAll must be called with a global RegExp TypeError: More arguments needed TypeError: null/undefined has no properties TypeError: property "x" is non-configurable and can't be deleted TypeError: Reduce of empty array with no initial value TypeError: setting getter-only property "x" TypeError: WeakSet key/WeakMap value 'x' must be an object or an unregistered symbol TypeError: X.prototype.y called on incompatible type URIError: malformed URI sequence Warning: -file- is being assigned a //# sourceMappingURL, but already has one Warning: unreachable code after return statement Misc JavaScript technologies overview Execution model Lexical grammar Iteration protocols Strict mode Template literals Trailing commas Deprecated features Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/sms-template#content-area | SMS Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors SMS Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors SMS Template OpenAI Open in ChatGPT How to design and publish SMS template. OpenAI Open in ChatGPT Design Template You can design SMS template on SuprSend with a simple form editor tool. You can add variables with Handlebarsjs language. You can check how the message will look in the preview section on the right side. The SMS template has 3 parts: Message type (Transactional, Promotional, Engagement), Header (template headers added in the SMS integration settings), Body (SMS template is added here). Once designed, you can save the SMS template by clicking on “Save” button. When you are ready, you can Publish Draft by providing a name to the version. This will create a version in ‘Pending Approval’ state. Every SMS template goes through an approval process, where the templates are submitted to the registered DLT portal for review, where the SMS is reviewed based on the DLT guidelines and SMS either gets approved or rejected. SuprSend handles the template approval process for you. All you have to do is create a template on SuprSend while following DLT template guidelines, and wait for the approval / rejection of template. Accordingly, the published template version’s state will move to Live or Rejected . Once the version goes Live , you can use the template to send to your users. SMS fields description Field Description Message Type There are 3 types of message - (1) Transactional - Service implicit or Informative messages which are triggered corresponding to a user’s action either done at the time of sending the message or based on past data. All other OTPs other than bank OTPs also fall in this category. e.g.- delivery updates, E-commerce website OTPs etc. (2) Promotional - All the marketing related messages where we have not taken any explicit consent from the user. e.g.- messages sent to promote or sell a product (3) Engagement - Service Explicit or Engagement messages which are triggered to re-engage the users back to platform like promoting new features and offers. e.g.- new feature promotion, discount offer messages to existing customers etc. Header Header should be registered with DLT. Separate headers would be there for all the message types Body SMS template added here should follow DLT template guidelines. Click here to view all DLT guidelines Please note that to send the SMS, you will need to integrate SMS vendor with SuprSend. Please visit the ‘Vendor Integration Guideline’ section to see vendors list and how to integrate them. Vendor Integration Required 📘 Please note that to send the SMS, you will need to integrate SMS vendor with SuprSend. Please visit the ‘Vendor Integration Guideline’ section to see vendors list and how to integrate them. Adding dynamic content in SMS There will always be the case where you would be required to add dynamic content to a template, so as to personalise it for your users. To achieve this, you can add variables in the template, which will be replaced with the dynamic content at the time of sending email. To send actual values to replace variables at the time of communication trigger, use one of our frontend or backend SDKs. Here is a step by step guide on how to add dynamic content in a template: 1 Declaring Variables in the global 'Mock data' button: If you are at this stage, it is assumed that you have declared the variables along with sample values in the global Mock data button. To see how to declare variables before using them in designing templates, refer to this section in the Templates documentation . 2 Using variables in the templates: Once the variables are declared, you can use them while designing template for any channel. We support handlebarsjs to add variables in the template. As a general rule, all the variables have to be entered within double curly brackets: {{variable\_name}} If you have declared the variables and added sample data in the global Mock data button, then they will come as auto-suggestions when you type a curly bracket { . This will remove the chances of error like variable mismatch at the time of template rendering. Note that you will be able to enter a variable name even when you have not declared it inside the Variables button. To manually enter the variable name, follow the handlerbarsjs guide here . Below are some examples of how to enter variables in the template design. For illustration, we are using the same sample variable names that we declared in the Templates section: json Copy Ask AI { "array" : [ { "product_name" : "Aldo Sling Bag" , "product_price" : "3,950.00" }, { "product_name" : "Clarles & Keith Women Slipper, Biege, 38UK" , "product_price" : "2,549.00" }, { "product_name" : "RayBan Sunglasses" , "product_price" : "7,899.00" } ], "event" : { "location" : { "city" : "Bangalore" , "state" : "KA" }, "order_id" : "11200123" , "first_name" : "Nikita" }, "product_page" : "https://www.suprsend.com" } To enter a nested variable, enter in the format {{var1.var2.var3}} . Eg. to refer to city in the example above, you need to enter {{event.location.city}} If you have any space in the variable name, enclose it in square bracket {{event.[first name]}} To refer to an array element, enter in format {{var1.[index].var2}} . Eg. to refer to product_name of the first element of the array array , enter {{array.[0].product_name}} At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user. Please note that the rest of the templates will be sent. Eg. if there is an error in rendering Android Push template, but SMS template is successfully rendered, Android Push notification will not be triggered, but SMS notification will be triggered by SuprSend. Was this page helpful? Yes No Suggest edits Raise issue Previous Whatsapp Template How to design whatsapp template using form editor. Next ⌘ I x github linkedin youtube Powered by On this page Design Template SMS fields description Adding dynamic content in SMS | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/Styling_basics | CSS styling basics - Learn web development | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Learn Core learning modules CSS styling basics Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) CSS styling basics Overview: Core learning modules Next CSS (Cascading Style Sheets) is used to style and layout web pages — for example, to alter the font, color, size, and spacing of your content, split it into multiple columns, or add animations and other decorative features. This module provides all the CSS fundamentals you'll need for now, including syntax, features, and techniques. In this article Prerequisites Tutorials and challenges Test your skills Additional tutorials See also Prerequisites Before starting this module, you should have a basic work environment set up (as detailed in Installing basic software ), and understand how to create and manage files (as detailed in Dealing with files ). You should also be familiar with HTML (work through our Structuring content with HTML module if not). Note: If you are working on a computer, tablet, or another device where you can't create files, you can try running the code in an online editor such as CodePen or JSFiddle . Tutorials and challenges What is CSS? CSS allows you to create great-looking web pages, but how does it work under the hood? This article explains what CSS is, what the basic syntax looks like, and how your browser applies CSS to HTML to style it. Getting started with CSS In this article, we will take a simple HTML document and apply CSS to it, learning some practical details of the language along the way. We will also review the CSS syntax features you've not looked at yet. Styling a biography page Challenge In this challenge you will style a simple biography page, testing you on some of the skills you learned in the last couple of lessons including writing selectors, coloring backgrounds, and text styling. We will also invite you to look up some basic CSS features that we haven't covered, to test your research skills. Basic CSS selectors In this article we'll recap some selector fundamentals, including the basic type, class, and ID selectors. Attribute selectors As you know from your study of HTML, elements can have attributes that give further detail about the element being marked up. In CSS you can use attribute selectors to target elements with certain attributes. This lesson will show you how to use these very useful selectors. Pseudo-classes and pseudo-elements The next set of selectors we will look at are referred to as pseudo-classes and pseudo-elements . There are a large number of these, and they often serve quite specific purposes. Once you know how to use them, you can look through the different types to see if there is something which works for the task you are trying to achieve. Combinators The final selectors we will look at are called combinators. Combinators are used to combine other selectors in a way that allows us to select elements based on their location in the DOM relative to other elements (for example, child or sibling). The box model Everything in CSS has a box around it, and understanding these boxes is key to being able to create more complex layouts with CSS, or to align items with other items. In this lesson, we will take a look at the CSS Box model . You'll get an understanding of how it works and the terminology that relates to it. Handling conflicts The aim of this lesson is to develop your understanding of some of the most fundamental concepts of CSS — the cascade, specificity, and inheritance — which control how CSS is applied to HTML and how conflicts between style declarations are resolved. Fixing blog page styles Challenge In this challenge we give you a basic blog page example that is partially styled. We need you to fix some problems with the existing CSS and add some styles to finish it off. Along the way we will test your knowledge of selectors, the box model, and conflicts/cascade. Values and units CSS rules contain declarations , which in turn are composed of properties and values. Each property used in CSS has a value type that describes what kind of values it is allowed to have. In this lesson, we will take a look at some of the most frequently used value types, what they are, and how they work. Sizing items in CSS Understanding how big the different features in your design will be is important. In this lesson we will summarize the various ways elements get a size via CSS and define a few terms about sizing that will help you in the future. Backgrounds and borders In this lesson, we will take a look at some of the creative things you can do with CSS backgrounds and borders. From adding gradients, background images, and rounded corners, backgrounds and borders are the answer to a lot of styling questions in CSS. Challenge: Sizing and decorating a content panel Challenge In this challenge you are provided with a lightly styled page structure that renders a content panel, with a heading at the top and a button bar at the bottom. We want you to follow the instructions to size and decorate it, producing an interesting layout as a result. Along the way, we'll test your knowledge of CSS values and units, sizing, and backgrounds and borders. Overflowing content Overflow is what happens when there is too much content to fit inside an element box. In this lesson, you will learn how to manage overflow using CSS. Images, media, and form elements In this lesson we will take a look at how certain special elements are treated in CSS. Images, other media, and form elements behave a little differently from regular boxes in terms of your ability to style them with CSS. Understanding what is and isn't possible can save some frustration, and this lesson will highlight some of the main things that you need to know. Styling tables Styling an HTML table isn't the most glamorous job in the world, but sometimes we all have to do it. This article explains how to make HTML tables look good, with some specific table styling techniques highlighted. Debugging CSS This article will give you guidance on how to go about debugging a CSS problem, and show you how the DevTools included in all modern browsers can help you to find out what is going on. Test your skills You will find "Test your skills" articles placed between the tutorial articles to check whether you have retained the most important information before you move on. If you want to explore all of these together, you can find them listed at Test your skills: CSS styling basics . Additional tutorials These tutorials are not part of the learning pathway, but they are interesting nonetheless — you should consider these as stretch goals, to optionally study when you are done with the main Core articles. Advanced styling effects This article acts as a box of tricks, providing an introduction to some interesting advanced styling features such as box shadows, blend modes, and filters. Cascade layers This lesson aims to introduce you to cascade layers , a more advanced feature that builds on the fundamental concepts of the CSS cascade and CSS specificity . Handling different text directions In recent years, CSS has evolved in order to better support different directionality of content, including right-to-left but also top-to-bottom content (such as Japanese) — these different directionalities are called writing modes. As you progress in your study and begin to work with layout, an understanding of writing modes will be very helpful to you, therefore we will introduce them in this article. Organizing CSS As you start to work on larger stylesheets and big projects you will discover that maintaining a huge CSS file can be challenging. In this article we will take a brief look at some best practices for writing your CSS to make it easily maintainable, and some of the solutions you will find in use by others to help improve maintainability. See also Learn HTML and CSS , Scrimba MDN learning partner Scrimba's Learn HTML and CSS course teaches you HTML and CSS through building and deploying five awesome projects, with fun interactive lessons and challenges taught by knowledgeable teachers. Write your first lines of CSS! , Scrimba MDN learning partner This interactive lesson provides a useful introduction to CSS syntax. Overview: Core learning modules Next Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 13, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Learn web development MDN curriculum Getting started modules Environment setup Installing software Browsing the web Code editors Dealing with files Command line Your first website What will it look like? Creating the content Styling the content Adding interactivity Publishing Web standards How the web works The web standards model How browsers load websites Soft skills Research and learning Collaboration and teamwork Workflows and processes Finding a job Core modules Structuring content with HTML Basic HTML syntax Web page metadata Headings and paragraphs Emphasis and importance Lists Test: HTML text basics Advanced text features Test: Advanced HTML text Challenge: Letter markup Structuring documents Creating links Test: Links Challenge: Bird watching site Images Test: Images Video and audio Test: Audio and video Challenge: Splash page Table basics Table accessibility Challenge: Planet data table Forms and buttons Test: Forms and buttons Challenge: Feedback form Debugging HTML Test: HTML tests index Additional tutorials Vector graphics Embedding technologies CSS styling basics What is CSS? CSS getting started Challenge: Biography page Basic selectors Attribute selectors Pseudo-classes and elements Combinators Test: Selectors Box model Test: Box model Handling conflicts Test: Cascade Challenge: Fixing blog styles Values and units Test: Values and units Sizing Test: Sizing Backgrounds and borders Test: Backgrounds and borders Overflow Test: Overflow Challenge: Sizing and decorating Images, media, forms Test: Images and forms Styling tables Challenge: Styling color scheme search Debugging CSS Test: Styling basics tests index Additional tutorials Advanced styling effects Cascade layers Multiple text directions Organizing your CSS CSS text styling Text and font fundamentals Styling lists Styling links Web fonts Challenge: Community school homepage CSS layout Introduction Floats Test: Floats Positioning Test: Positioning Flexbox Test: Flexbox CSS grid layout Test: CSS grid Challenge: Fundamental layout Responsive web design Media queries Test: RWD & media queries Challenge: mobile-first Test: Layout tests index Additional tutorials Multiple-column layout Practical positioning examples Legacy layout methods Supporting older browsers Dynamic scripting with JavaScript What is JavaScript? JavaScript walkthrough Troubleshooting Variables Test: Variables Numbers and operators Test: Math Strings String methods Test: Strings Arrays Test: Arrays Challenge: Story generator Conditionals Test: Conditionals Loops Test: Loops Functions Build your own function Function return values Test: Functions Events Event bubbling Test: Events Objects Test: Objects DOM scripting Challenge: Image gallery Network requests JSON Test: JSON Challenge: House data UI Debugging and error handling Test: JavaScript tests index JavaScript frameworks and libraries Introduction Framework features React getting started React ToDo app React components React events and state React editing, filtering, conditional UI React accessibility React resources Accessibility What is accessibility? Accessibility tools Accessible HTML Test: HTML a11y Accessible CSS and JS Test: CSS/JS a11y WAI-ARIA Test: WAI-ARIA Accessible multimedia Mobile accessibility Challenge: A11y debugging Test: A11y tests index Design for developers Version control Extension modules Advanced JavaScript objects Object prototypes Object-oriented programming Classes in JavaScript Test: Object-oriented JavaScript Object building practice Challenge: Bouncing balls features Test: OOJS tests index Client-side web APIs Introduction Video and audio Drawing graphics Client-side storage Third-party APIs Asynchronous JavaScript Introduction Using promises Implementing promise-based APIs Introducing workers Challenge: Animation sequence Web forms Your first form How to structure a web form Basic native form controls The HTML5 input types Other form controls Styling web forms Advanced form styling Customizable selects UI pseudo-classes Client-side form validation Sending form data Additional tutorials Custom form controls JS form submission Forms in legacy browsers UI methods & controls Understanding client-side tools Overview Package management Sample toolchain Deploying our app Server-side websites First steps Introduction Client-server overview Server-side frameworks Website security Django (Python) Django introduction Dev environment setup 1: Local library tutorial 2: Skeleton website 3: Models 4: Django admin site 5: Home page 6: Generic list and detail views 7: Sessions framework 8: Authentication and permissions 9: Forms 10: Testing 11: Deploying Django security Challenge: Django blog Express (Node.js) Express/Node introduction Dev environment setup 1: Local library tutorial 2: Skeleton website 3: Using databases with Mongoose 4: Routes and controllers 5: Displaying data 6: Working with forms 7: Deploying Additional tutorials Apache .htaccess Server MIME type config Plain Node.js server Web performance The "why" of web performance What is web performance? Perceived performance Measuring performance Multimedia: Images Multimedia: video Performant JavaScript Performant HTML Performant CSS Performance business case Best practices & tips Testing Introduction Testing strategies Common HTML and CSS problems Feature detection Automated testing Automation environment setup Further resources How to solve common problems Common CSS problems Common HTML problems Common JavaScript problems Design and accessibility Tools and setup Web mechanics About Resources for educators Changelog Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://www.youtube.com/watch?v=FjMbVuAyWzg | 🎙️ Navigating change and evolving with purpose with Pamela Meyer, Author of Staying in the Game - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x4d09b50ab1d85af2"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtPTWxWSTZvbWhqNCjWjZjLBjIKCgJLUhIEGgAgLA%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRTFQE8JKD4Vcb3JxEkYyIbHLprwiO8l73zhHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","markerRenderer","chapterRenderer","notificationActionRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","macroMarkersListRenderer","macroMarkersListItemRenderer","toggleButtonRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionCourseSectionRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","topicLinkRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtPTWxWSTZvbWhqNCjWjZjLBjIKCgJLUhIEGgAgLA%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwjC0cDukIiSAxXDgVYBHUgfFn4yDHJlbGF0ZWQtYXV0b0i4tsmB7urGmRaaAQUIAxD4HcoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjC0cDukIiSAxXDgVYBHUgfFn4yDHJlbGF0ZWQtYXV0b0i4tsmB7urGmRaaAQUIAxD4HcoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjC0cDukIiSAxXDgVYBHUgfFn4yDHJlbGF0ZWQtYXV0b0i4tsmB7urGmRaaAQUIAxD4HcoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"🎙️ Navigating change and evolving with purpose with Pamela Meyer, Author of Staying in the Game"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 67회"},"shortViewCount":{"simpleText":"조회수 67회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"COECELW0CRgAIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC0ZqTWJWdUF5V3pnGmBFZ3RHYWsxaVZuVkJlVmQ2WjBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDBacVRXSldkVUY1VjNwbkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"COECELW0CRgAIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}}],"trackingParams":"COECELW0CRgAIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"3","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COwCEKVBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}},{"innertubeCommand":{"clickTrackingParams":"COwCEKVBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CO0CEPqGBCITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CO0CEPqGBCITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"FjMbVuAyWzg"},"likeParams":"Cg0KC0ZqTWJWdUF5V3pnIAAyDAjWjZjLBhCT_qS8Aw%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CO0CEPqGBCITCMLRwO6QiJIDFcOBVgEdSB8Wfg=="}}}}}}}]}},"accessibilityText":"다른 사용자 3명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COwCEKVBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"4","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COsCEKVBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}},{"innertubeCommand":{"clickTrackingParams":"COsCEKVBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"FjMbVuAyWzg"},"removeLikeParams":"Cg0KC0ZqTWJWdUF5V3pnGAAqDAjWjZjLBhD906a8Aw%3D%3D"}}}]}},"accessibilityText":"다른 사용자 3명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COsCEKVBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"COECELW0CRgAIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","isTogglingDisabled":true}},"likeStatusEntityKey":"EgtGak1iVnVBeVd6ZyA-KAE%3D","likeStatusEntity":{"key":"EgtGak1iVnVBeVd6ZyA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COkCEKiPCSITCMLRwO6QiJIDFcOBVgEdSB8Wfg=="}},{"innertubeCommand":{"clickTrackingParams":"COkCEKiPCSITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"COoCEPmGBCITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COoCEPmGBCITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"FjMbVuAyWzg"},"dislikeParams":"Cg0KC0ZqTWJWdUF5V3pnEAAiDAjWjZjLBhDT06m8Aw%3D%3D"}},"idamTag":"66425"}},"trackingParams":"COoCEPmGBCITCMLRwO6QiJIDFcOBVgEdSB8Wfg=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COkCEKiPCSITCMLRwO6QiJIDFcOBVgEdSB8Wfg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COgCEKiPCSITCMLRwO6QiJIDFcOBVgEdSB8Wfg=="}},{"innertubeCommand":{"clickTrackingParams":"COgCEKiPCSITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"FjMbVuAyWzg"},"removeLikeParams":"Cg0KC0ZqTWJWdUF5V3pnGAAqDAjWjZjLBhD5iaq8Aw%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COgCEKiPCSITCMLRwO6QiJIDFcOBVgEdSB8Wfg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"COECELW0CRgAIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","isTogglingDisabled":true}},"dislikeEntityKey":"EgtGak1iVnVBeVd6ZyA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgtGak1iVnVBeVd6ZyD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COYCEOWWARgDIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}},{"innertubeCommand":{"clickTrackingParams":"COYCEOWWARgDIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtGak1iVnVBeVd6Z6ABAQ%3D%3D","commands":[{"clickTrackingParams":"COYCEOWWARgDIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"COcCEI5iIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COYCEOWWARgDIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"COQCEOuQCSITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"COUCEPuGBCITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DFjMbVuAyWzg\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COUCEPuGBCITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"COUCEPuGBCITCMLRwO6QiJIDFcOBVgEdSB8Wfg=="}}}}}},"trackingParams":"COQCEOuQCSITCMLRwO6QiJIDFcOBVgEdSB8Wfg=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"COICEOuQCSITCMLRwO6QiJIDFcOBVgEdSB8Wfg=="}},{"innertubeCommand":{"clickTrackingParams":"COICEOuQCSITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"COMCEPuGBCITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DFjMbVuAyWzg\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COMCEPuGBCITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"COMCEPuGBCITCMLRwO6QiJIDFcOBVgEdSB8Wfg=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"COICEOuQCSITCMLRwO6QiJIDFcOBVgEdSB8Wfg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"COECELW0CRgAIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","superTitleLink":{"runs":[{"text":"The Agile in Action Podcast with Bill Raymond","navigationEndpoint":{"clickTrackingParams":"COECELW0CRgAIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLWzwUIYZpnJsGnFUCmugOjrxYFOFNF93B","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLWzwUIYZpnJsGnFUCmugOjrxYFOFNF93B"}}}]},"dateText":{"simpleText":"2023. 10. 10."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"2년 전"}},"simpleText":"2년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Bill Raymond","navigationEndpoint":{"clickTrackingParams":"COACEOE5IhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/@bill-raymond","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCo63gWfWRfEciJ98mJLIU0Q","canonicalBaseUrl":"/@bill-raymond"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"COACEOE5IhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/@bill-raymond","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCo63gWfWRfEciJ98mJLIU0Q","canonicalBaseUrl":"/@bill-raymond"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 7.01천명"}},"simpleText":"구독자 7.01천명"},"trackingParams":"COACEOE5IhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCo63gWfWRfEciJ98mJLIU0Q","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CNECEJsrIhMIwtHA7pCIkgMVw4FWAR1IHxZ-KPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Bill Raymond을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Bill Raymond을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CN8CEPBbIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CN4CEPBbIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CNcCEJf5ASITCMLRwO6QiJIDFcOBVgEdSB8Wfg==","command":{"clickTrackingParams":"CNcCEJf5ASITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CNcCEJf5ASITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CN0CEOy1BBgDIhMIwtHA7pCIkgMVw4FWAR1IHxZ-MhJQUkVGRVJFTkNFX0RFRkFVTFTKAQQI2pIS","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ282M2dXZldSZkVjaUo5OG1KTElVMFESAggBGAAgBFITCgIIAxILRmpNYlZ1QXlXemcYAA%3D%3D"}},"trackingParams":"CN0CEOy1BBgDIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CNwCEO21BBgEIhMIwtHA7pCIkgMVw4FWAR1IHxZ-MhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQQI2pIS","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ282M2dXZldSZkVjaUo5OG1KTElVMFESAggDGAAgBFITCgIIAxILRmpNYlZ1QXlXemcYAA%3D%3D"}},"trackingParams":"CNwCEO21BBgEIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CNgCENuLChgFIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CNgCENuLChgFIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CNkCEMY4IhMIwtHA7pCIkgMVw4FWAR1IHxZ-","dialogMessages":[{"runs":[{"text":"Bill Raymond"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CNsCEPBbIhMIwtHA7pCIkgMVw4FWAR1IHxZ-MgV3YXRjaMoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"CgIIAxILRmpNYlZ1QXlXemcYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CNsCEPBbIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CNoCEPBbIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CNgCENuLChgFIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CNECEJsrIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNYCEP2GBCITCMLRwO6QiJIDFcOBVgEdSB8WfjIJc3Vic2NyaWJlygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DFjMbVuAyWzg%26continue_action%3DQUFFLUhqbE9yRUlpRE50WVRTWmVwOEYxUjl6MHpvd0hud3xBQ3Jtc0tuY3VKTWJZMFpDUGczN0EwUVFXVzJVUDZjUW41YnpWMmJwNlZZNEpoRzEtZ1dwMDdLeUVVeTdhTDgwX3M1bHVLR2tPODBaU0R4SHhIQU1DRUMtX0lmWWhzTzVwMzdBczA3NzVQSjR3ZmdiSzFMcWgzbFNsSnVjT0RucTA1bXVhRi16Z1RGQnRBRkdRSnpPTzZZUkpxRWRPSXJZcmo1NWpLYXA1eTZuTV9ZUGV4bFdMV0xYbC1PRzlKR2hkdGhnS3VTOUpLb0g\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNYCEP2GBCITCMLRwO6QiJIDFcOBVgEdSB8WfsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbE9yRUlpRE50WVRTWmVwOEYxUjl6MHpvd0hud3xBQ3Jtc0tuY3VKTWJZMFpDUGczN0EwUVFXVzJVUDZjUW41YnpWMmJwNlZZNEpoRzEtZ1dwMDdLeUVVeTdhTDgwX3M1bHVLR2tPODBaU0R4SHhIQU1DRUMtX0lmWWhzTzVwMzdBczA3NzVQSjR3ZmdiSzFMcWgzbFNsSnVjT0RucTA1bXVhRi16Z1RGQnRBRkdRSnpPTzZZUkpxRWRPSXJZcmo1NWpLYXA1eTZuTV9ZUGV4bFdMV0xYbC1PRzlKR2hkdGhnS3VTOUpLb0g","idamTag":"66429"}},"trackingParams":"CNYCEP2GBCITCMLRwO6QiJIDFcOBVgEdSB8Wfg=="}}}}}},"subscribedEntityKey":"EhhVQ282M2dXZldSZkVjaUo5OG1KTElVMFEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CNECEJsrIhMIwtHA7pCIkgMVw4FWAR1IHxZ-KPgdMgV3YXRjaMoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"EgIIAxgAIgtGak1iVnVBeVd6Zw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CNECEJsrIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CNECEJsrIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CNMCEMY4IhMIwtHA7pCIkgMVw4FWAR1IHxZ-","dialogMessages":[{"runs":[{"text":"Bill Raymond"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CNUCEPBbIhMIwtHA7pCIkgMVw4FWAR1IHxZ-KPgdMgV3YXRjaMoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"CgIIAxILRmpNYlZ1QXlXemcYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CNUCEPBbIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CNQCEPBbIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}],"timedAnimationData":{"animationTiming":[2112280],"macroMarkersIndex":[0],"animationDurationSecs":1.5,"borderStrokeThicknessDp":2,"borderOpacity":1,"fillOpacity":0,"trackingParams":"CNICEPBbIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","animationOrigin":"ANIMATION_ORIGIN_SMARTIMATION"}}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Unpack the essentials of embodied agile leadership so you can thrive amidst constant change.\n\nIn today's podcast, I share this insightful conversation with leadership agility expert Pamela Meyer about her latest book, \"Staying in the Game: Leading and Learning with Agility for a Dynamic Future.\"\n\nPamela and I share practical advice for leaders cultivating the mindsets and practices needed to stay agile, resilient, and continuously learning amidst constant change.\n\nHere is what you will learn:\n\n✅ The four dynamics for staying agile: meaningful identity, community, competition, and commitment\n✅ Why leaders need a learning vs. controlling mindset\n✅ Examples of agile leaders in action\n🎉 How to avoid losing momentum by connecting to your intrinsic motivations\n\n🔗 To get access to the links mentioned in this podcast, please visit the Agile in Action podcast website here:\nhttps://agileinaction.com/agile-in-ac...\n\n🎧 Listen now\nApple Podcasts: https://apple.co/3e35K9O\nGoogle: https://bit.ly/3sFYpBe\nSpotify: https://spoti.fi/3e40d34\n\nKey moments:\n00:00 Podcast intro\n00:13 Introducing Pamela Meyer\n01:26 Pamela's books\n02:56 Avoid losing momentum\n05:24 Introducing the Four Dynamics\n07:00 Meaningful identity\n09:03 Competition\n15:26 Commitment\n18:24 Case studies\n22:29 Plan bias \n25:25 Defensiveness vs. commitment\n31:19 Improvement takeaways\n31:19 Ideas for improvement\n34:09 How to reach Pamela Meyer","commandRuns":[{"startIndex":879,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-SLi2yYHu6saZFsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa24xaHR6Y3JqVmhscUFZQnNHWlZONHJXcHFrZ3xBQ3Jtc0tsREs2akxmM1BhQWM5NWZvRWZBTG5WdTZ6aUd2TUZJdXR1UjZRV2ZFOXpWZGo1QkhxaTloa2RZZklHcEtvc2p6Z2J3ZktUU2htaGRRcXhFS3FBNGJsT25aT0xjVXU1Yi1LOUFBRVdTZWZmUnFVUlNycw\u0026q=https%3A%2F%2Fagileinaction.com%2Fagile-in-action-podcast%2F2023%2F10%2F10%2Fnavigating-change-and-evolving-with-purpose.html\u0026v=FjMbVuAyWzg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa24xaHR6Y3JqVmhscUFZQnNHWlZONHJXcHFrZ3xBQ3Jtc0tsREs2akxmM1BhQWM5NWZvRWZBTG5WdTZ6aUd2TUZJdXR1UjZRV2ZFOXpWZGo1QkhxaTloa2RZZklHcEtvc2p6Z2J3ZktUU2htaGRRcXhFS3FBNGJsT25aT0xjVXU1Yi1LOUFBRVdTZWZmUnFVUlNycw\u0026q=https%3A%2F%2Fagileinaction.com%2Fagile-in-action-podcast%2F2023%2F10%2F10%2Fnavigating-change-and-evolving-with-purpose.html\u0026v=FjMbVuAyWzg","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":951,"length":24,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-SLi2yYHu6saZFsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbjNqN0dndGlPSGJUVFoxU1V1Vm1WcGJhT3NPQXxBQ3Jtc0tuQUtNTGdHbVB6dE4xY1gxSmdWUlYwM1hIREtvVTg2S2pHbTNERzRMVWZ5SWVvMzVmUmlta3VMbnB3OGFtR2w0akhGa2c2MmlLNV9RNTV1NWh4TTlOR2FxVEIwREgzWUxCeVlYNHVuUzJqeXlGOEhpdw\u0026q=https%3A%2F%2Fapple.co%2F3e35K9O\u0026v=FjMbVuAyWzg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbjNqN0dndGlPSGJUVFoxU1V1Vm1WcGJhT3NPQXxBQ3Jtc0tuQUtNTGdHbVB6dE4xY1gxSmdWUlYwM1hIREtvVTg2S2pHbTNERzRMVWZ5SWVvMzVmUmlta3VMbnB3OGFtR2w0akhGa2c2MmlLNV9RNTV1NWh4TTlOR2FxVEIwREgzWUxCeVlYNHVuUzJqeXlGOEhpdw\u0026q=https%3A%2F%2Fapple.co%2F3e35K9O\u0026v=FjMbVuAyWzg","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":984,"length":22,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-SLi2yYHu6saZFsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbENIdzU0QVNIdFNveVhmc0JGVUE4bmpROVJmUXxBQ3Jtc0trSkN3OGVOLXNVNXVOT2d2N0IwOWxIWU9yUEdsSGlZTUU0Q1d4bmhJVGZuS3NvQ0FIR180azl3OWticGxCU24xMDg4ZUdkRXdNcWE2ekdpQ0dIc0MwemNfTkZXZk9oOTlMRWdLWmNIZlVydV9JS1hIbw\u0026q=https%3A%2F%2Fbit.ly%2F3sFYpBe\u0026v=FjMbVuAyWzg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbENIdzU0QVNIdFNveVhmc0JGVUE4bmpROVJmUXxBQ3Jtc0trSkN3OGVOLXNVNXVOT2d2N0IwOWxIWU9yUEdsSGlZTUU0Q1d4bmhJVGZuS3NvQ0FIR180azl3OWticGxCU24xMDg4ZUdkRXdNcWE2ekdpQ0dIc0MwemNfTkZXZk9oOTlMRWdLWmNIZlVydV9JS1hIbw\u0026q=https%3A%2F%2Fbit.ly%2F3sFYpBe\u0026v=FjMbVuAyWzg","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":1016,"length":24,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-SLi2yYHu6saZFsoBBAjakhI=","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbUxrVFY1U1BRWnlIdGpCNXFQM2hkczA3dkJNUXxBQ3Jtc0tsNGVabXJCYy1lVldjc3VoeWU3bF9kZmkxbGpZNmJOdk40bl9wRjY3SjFrM1p3cVNOMzl4QnBJX01ZY3RGd1d1eC1DLVJhdzdZaWFOakNuNTFiaENpS2NTcFRmVm0tcG1mLWhGSE1jODJZQ243UWNYcw\u0026q=https%3A%2F%2Fspoti.fi%2F3e40d34\u0026v=FjMbVuAyWzg","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbUxrVFY1U1BRWnlIdGpCNXFQM2hkczA3dkJNUXxBQ3Jtc0tsNGVabXJCYy1lVldjc3VoeWU3bF9kZmkxbGpZNmJOdk40bl9wRjY3SjFrM1p3cVNOMzl4QnBJX01ZY3RGd1d1eC1DLVJhdzdZaWFOakNuNTFiaENpS2NTcFRmVm0tcG1mLWhGSE1jODJZQ243UWNYcw\u0026q=https%3A%2F%2Fspoti.fi%2F3e40d34\u0026v=FjMbVuAyWzg","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":1055,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"0초"}}},{"startIndex":1075,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=13s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":13,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=13\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"13초"}}},{"startIndex":1106,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=86s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":86,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=86\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"1분 26초"}}},{"startIndex":1127,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=176s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":176,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=176\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"2분 56초"}}},{"startIndex":1155,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=324s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":324,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=324\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"5분 24초"}}},{"startIndex":1191,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=420s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":420,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=420\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"7분"}}},{"startIndex":1217,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=543s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":543,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=543\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"9분 3초"}}},{"startIndex":1235,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=926s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":926,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=926\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"15분 26초"}}},{"startIndex":1252,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=1104s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":1104,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=1104\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"18분 24초"}}},{"startIndex":1271,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=1349s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":1349,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=1349\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"22분 29초"}}},{"startIndex":1288,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=1525s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":1525,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=1525\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"25분 25초"}}},{"startIndex":1323,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=1879s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":1879,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=1879\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"31분 19초"}}},{"startIndex":1351,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=1879s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":1879,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=1879\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"31분 19초"}}},{"startIndex":1379,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CNACEM2rARgBIhMIwtHA7pCIkgMVw4FWAR1IHxZ-ygEECNqSEg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FjMbVuAyWzg\u0026t=2049s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FjMbVuAyWzg","continuePlayback":true,"startTimeSeconds":2049,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=16331b56e0325b38\u0026ip=1.208.108.242\u0026osts=2049\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"34분 9초"}}}],"styleRuns":[{"startIndex":0,"length":879,"styleRunExtensions":{"styleRunColorMapExte | 2026-01-13T08:48:25 |
https://t.co/L9eCOAkoTT | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/Privacy | Privacy on the web | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Privacy on the web Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 한국어 中文 (简体) Privacy on the web People use websites for several important tasks such as banking, shopping, entertainment, and paying their taxes. In doing so, they are required to share personal information with those sites. Users place a certain level of trust in the sites they share their data with. If that information fell into the wrong hands, it could be used to exploit users, for example by profiling them, targeting them with unwanted ads, or even stealing their identity or money. Modern browsers already have a wealth of features to protect users' privacy on the web, but that's not enough. To create a trustworthy and privacy-respecting experience, developers need to educate their site users in good practices (and enforce them). Developers should also create sites that collect as little data from users as possible, use the data responsibly, and transport and store it securely. In this article, we: Define privacy and important related terms. Examine browser features that automatically protect user privacy. Look at what developers can do to create privacy-respecting web content that minimizes the risk of users' personal information/data being obtained unexpectedly by third parties. In this article Defining privacy terms and concepts Privacy features provided by browsers Privacy considerations for client-side developers Collect data ethically Cut down on tracking Carefully manage third-party resources Protect user data See also Defining privacy terms and concepts Before we look at the various privacy and security features available to use on the web, let's define some important terms. Privacy and its relationship with security It is hard to talk about privacy without also talking about security — they are closely related, and you can't really create privacy-respecting websites without good security. Therefore, we shall define both. Privacy refers to the act of giving users the right to control how their data is collected, stored, and used, and not using it irresponsibly. For example, you should clearly communicate to your users what data you are collecting, who it will be shared with, and how it will be used. Users must be given a chance to consent to your terms of data usage, have access to all of their data that you are storing, and delete it if they no longer wish you to have it. You must also comply with your own terms: nothing erodes user trust like having their data used and shared in ways they never consented to. And this isn't just ethically wrong; it could be against the law. Many parts of the world now have legislation that protects consumer privacy rights (for example the EU's GDPR ). Security is the act of keeping private data and systems protected against unauthorized access. This includes both company (internal) data, and user and partner (external) data. It is no use having a robust privacy policy that makes your users trust you if your security is weak and malicious parties can steal their data anyway. Personal and private information Personal information is any information that describes a user. Examples include: Postal address, email address, phone number, or other contact information Passport number, bank account, credit card, social security number, or other official identifiers Physical attributes such as height, gender expression, weight, hair color, or age Health information such as medical history, allergies, or ongoing conditions Usernames, when they can be linked to an individual Hobbies, interests, or other personal preferences Biometric data such as fingerprints or facial recognition data Private information is any information that users do not want shared publicly and must be kept private (i.e., information that is accessible only by a certain group of authorized users). Some private data is private by law (for example medical data), and some is private more by personal preference. Personally identifiable information Following on from the above section, personally identifiable information (PII) is information that can be used, in whole or in part, to track down and/or identify a specific person. For example, if a site leaks a list of users' names and zip codes online, a bad actor could almost certainly use this information to find their full addresses. Even if a full-scale leak does not happen, it is still possible to identify users through less obvious means, such as the browsers they are using, the devices they are using, specific fonts they have installed, and so on. Tracking Tracking refers to the process of recording a user's activity across many different websites. This can be done in various ways, for example: Looking at multiple third-party cookies set across different sites where third-party content is embedded to find out various information points about the user. Looking at the Referer header to see where a user has navigated from. Including parameters on the URLs of inbound links (for example in embedded ads linking to product pages, or marketing emails) that can reveal to the linked site where the link originated from, what marketing campaign it is part of, the email address or other identifier of the user that clicked on it, etc. This process is referred to as link decorating , and results in link URLs that look like this: https://example.com/article/?id=62yhgt1a&campaign=902 . Redirect tracking, which involves trackers momentarily (and imperceptibly) redirecting a user to their website to use first-party storage to track that user across websites. This allows trackers to get around third-party cookies being blocked. For example, if you have read a product review and want to click through to buy it, you might unwittingly navigate to the redirect tracker first, then to the retailer. This means the tracker is loaded as a first party, and can associate tracking data with the identifiers they have stored in their first-party cookies before forwarding you to the retailer. Tracking data can be used to build a profile of a user and their interests and preferences, which is usually bad and can be annoying to various degrees. For example: Targeted ads : Everyone has had the unnerving experience of researching some items to buy on one device and then suddenly being bombarded by adverts for the same products on all their other devices. Selling or sharing data : Some third parties have been known to compile tracking data and then sell it to/share it with others to use for various purposes, like targeted ads. This is obviously highly unethical and may also be illegal, depending on where in the world it happens. Prejudice via data : In the worst cases, sharing data could result in the user being unfairly disadvantaged. For example, imagine an insurance company finding out data points about a potential customer that they didn't consent to share, and using them as a justification for increasing insurance premiums. Fingerprinting A process very closely related to tracking is fingerprinting : this specifically refers to identifying users by building up a store of data points about them that differentiate them from other users. This could be anything from cookie contents to what browser they are using and what fonts they have installed locally. Modern browsers take steps to help prevent fingerprinting-based attacks by either not allowing information to be accessed or, where the information must be made available, by introducing variations or "noise" that prevent it from being used for identification purposes. For example, if a website queries a user's browser for the elapsed time, a comparison of that time to the time reported by the server might be useful as a factor in fingerprinting. Because of this, browsers typically introduce a small amount of variability to timers to make them less useful for identifying the user's system. Note: See Fingerprinting on web.dev for additional useful information. Privacy features provided by browsers Browser vendors are aware of the need to protect user privacy and the negative effects of tracking, fingerprinting, etc., on user experience. To this end, they have implemented various features that enhance privacy protection and/or mitigate threats. In this section, we look at different categories of privacy protection that browsers apply automatically. HTTPS by default Transport Layer Security (TLS) provides security and privacy by encrypting data during transport over the network and is the technology behind the HTTPS protocol. TLS is good for privacy because it stops third parties from being able to intercept transmitted data and use it maliciously, for example for tracking. All browsers are moving towards requiring HTTPS by default; this is practically the case already because you can't do much on the web without this protocol. Related topics are as follows: Certificate Transparency An open standard for monitoring and auditing certificates, creating a database of public logs that can be used to help identify incorrect or malicious certificates. HTTP Strict Transport Security (HSTS) HSTS is used by servers to let them protect themselves from protocol downgrade and cookie hijack attacks by letting sites tell clients that they can only use HTTPS to communicate with the server. HTTP/2 While HTTP/2 technically does not have to use encryption, most browser developers support it only when used with HTTPS; so in that regard, it can be thought of as a feature to enhance security/privacy. Opt-in for "powerful features" So-called "powerful" web API features that provide access to potentially sensitive data and operations are available only in secure contexts , which basically means HTTPS-only. Not only that, but these web features are gated behind a system of user permissions. Users have to explicitly opt in to features like allowing notifications, accessing geolocation data, making the browser go into fullscreen mode, accessing media streams from webcams, using web payments, etc. Anti-tracking technology Browsers have implemented several anti-tracking features that automatically enhance their users' privacy protection. Many of these block or limit the ability of third-party sites embedded in <iframe> s to access cookies set on the top-level domain, run tracking scripts, etc. The Set-Cookie header SameSite attribute's default value has been updated to Lax , to provide better protection against tracking and CSRF attacks. See Controlling third-party cookies with SameSite for more information. Browsers have all started to block third-party cookies by default. See How do browsers handle third-party cookies? for more details. Browsers are implementing technologies to allow third-party cookies only in certain circumstances that do not damage privacy, or to implement common use cases that currently require third-party cookies in alternative ways. See Transitioning from third-party cookies . Several browsers strip out known tracking parameters from URLs — this includes Firefox, Safari, and Brave. Browser extensions also help to do this, for example ClearURLs . Browsers have implemented redirect tracking protection . Privacy considerations for client-side developers There are several actions web developers can and should take to improve privacy for their users. The below sections discuss the most important ones. Some of the categories are not purely technical tasks as such and will involve collaboration with other team members. Collect data ethically Companies collect lots of different data from their users for a variety of different reasons: Usernames, passwords, emails, etc. for authentication purposes. Emails, postal addresses, and phone numbers for communication. Age, gender, geographical location, favorite pastimes, and a host of other PII for anything from site personalization to customer satisfaction surveys. Browsing habits on their sites and other sites, to measure page and feature success metrics. And so much more. When collecting data from your customers, you have an opportunity to behave with integrity, show them that you are trustworthy, and build a great relationship with them, in turn, improving your brand and your chance of success. The ethics of data collection can be broken down into three simple principles: Don't collect more data than you need Communicate clearly how you are going to use the data you collect Delete the data once you have finished with it Note: The tips provided below make for a better, more privacy-aware user experience, but many of them are required by law to comply with regulations, for example the GDPR in the EU. You should make sure to find out what regulations apply to you in your locale, and what you need to do to comply with them. Don't collect more data than you need It is tempting to ask for a lot of data from your users because you think it might be useful in the future. However, every bit of extra data you collect adds risk to your users' privacy and increases the chance that they will abandon the step they are performing (whether it is filling out a survey or signing up for a service). It is good to anonymize data. You should also consider whether you can get what you need by making your data request less granular. As an example, instead of asking a user their favorite products, you could ask them to select between more general categories. The best way to protect user privacy though, is to minimize the data you collect. Referring to the previous example, you could infer the same data by looking at user purchase history. As another example, users appreciate being able to buy products anonymously. You shouldn't force them to sign up for an account; if it's not necessary for the service to operate, it should be their choice. Communicate clearly how you are going to use the data you collect Once you have decided what data you are going to collect, you should publish a privacy policy on your site that clearly states: Data that you collect Ways in which you use the data Parties with whom you tend to share the data, if at all, and a declaration that you will ask for user consent before sharing The duration for which you keep the data before it is deleted Ways in which users can view the data you have collected from them and delete it if they want to When providing you with data, your users should be given an opportunity to read your privacy policy, and consent to it. They should be able to control if they are happy with this and agree to your terms. And as indicated above, they should also get to see what data of theirs you have collected, and delete it if they want to. When you've published your privacy policy, you need to make sure that you comply with it — doing what you say you are going to do is very important in building user trust. You should only collect the data you say you'll collect, and only use it for the purpose you say you'll use it for. If someone from your company comes up with a clever new way to use existing data, that still isn't OK under the terms of your policy if it doesn't specify that you'll use it for that purpose. If users consented to the use of their data for a specific purpose and that purpose expands, you may have to consider obtaining new consent. Delete the data once you have finished with it Earlier on, we mentioned giving users a way to see what data of theirs you have collected, and delete it if they want to. You could possibly do this as part of the same experience they can use to delete their account (their data goes with it), or make them two separate options. Either way, the options should be easy to find. Allowing the user to choose when significant portions of data get deleted is very empowering, and builds trust, but there may be some bits of data that you will want to handle deletion of yourself. For example, some data might only be used for a few hours or minutes and then deleted, like data that is used during the administration of a user's session while they are logged in. Note: The Clear-Site-Data HTTP response header is very useful for clearing short-lived user data — it instructs the browser to clear out its cache and/or cookies and/or storage (e.g., Web Storage or IndexedDB data). For example, you might get your server to send it along with a "logged out confirmation" page so that once the user is logged out, their data is safely removed. Cut down on tracking Earlier on we discussed tracking, and some of the unethical purposes it is used for. We shouldn't have to spell out how such uses can erode user trust; wherever possible, you should only use potential tracking mechanisms like third-party cookies for ethical uses, such as transferring sign-in or other personalization status across sites. Also recall from earlier that browsers are all starting to block third-party cookies by default, while implementing alternative technologies to achieve common use case. It is a good idea to prepare for this, by limiting the amount of tracking activities you rely on, and/or implementing desired information persistence in other ways. See Transitioning from third-party cookies for more information. Carefully manage third-party resources Of course, it would be easy to manage privacy if you were only worried about resources you have created (code, cookies, sites, etc.). The real challenge comes from the fact that your site will likely use third-party resources. This can include third-party content embedded in <iframe> s, libraries, frameworks, APIs, externally-hosted resources such as images and videos, etc. Third-party resources are an essential part of modern web development, they provide a lot of power. However, any third-party resource you allow onto your site potentially has the same permissions as your own resources; it all depends on how it is included on your site: JavaScript running inside third-party content embedded in your site via an <iframe> is separated by same-origin policy , meaning that it wouldn't have access to other scripts and data included in the top-level browsing context. However, a third-party script included directly in your page via a <script> element would have access to your other scripts and data, whether it was hosted on your site or another site. It would effectively be first-party code. A malicious script included in this way could secretly steal your users' data, for example sending it off to a third-party server. It is important to audit all of the third-party resources you use on your site. Make sure you know what data they collect, what requests they make and to whom, and what their privacy policies are. Your carefully designed privacy policy is useless if you use a third-party script that violates it. Note: There are various tools out there that can help you build up a picture of what requests a site is making, for example the Request Map Generator . Once you have audited your third-party resources and understand what they are doing, you should then consider their negatives as a trade-off for the value they bring. If a third-party script is free and really useful but collects quite a lot of user data, you could: Accept that trade-off, update your privacy policy to include details of it, and hope that it doesn't impact your users' trust too much. Look for an alternative, less data-hungry third-party tool. Build your own tool. The following list provides some tips on how to mitigate privacy risks inherent with using third-party resources: When embedding third-party resources, consider if there is a way to achieve the same or a similar effect with less privacy impact. For example, it might be fun to have a social media post viewer embedded on your site, but is it really necessary? Wouldn't a link to your social media page be sufficient? Also, some third-party services have privacy-enhancing options. See, for example, YouTube's Embed videos & playlists > Turn on privacy-enhanced mode . Where possible, you should block third parties from receiving a Referer header when you make requests to them. This can be done in a pretty granular way, for example by including rel="noreferrer" on external links. Or, you could set this more globally for the page or site, for example by using the Referrer-Policy header. Note: See also Referer header: privacy and security concerns . Use the Permissions-Policy HTTP header to control access to API "powerful features" (such as notifications, geolocation data, accessing media streams from webcams, etc.). This can be useful for privacy because it stops third-party sites from doing unexpected things with these features, and users don't want to be unnecessarily bombarded by permission prompts that they may not understand. You can also control usage of "powerful features" inside third-party sites embedded inside <iframe> elements by specifying permissions policies inside an allow attribute on the <iframe> itself. Note: See also our Permissions-Policy guide for more information and examples, and permissionspolicy.com for useful tools including a policy generator. Use the <iframe> sandbox attribute to allow or disallow usage of certain features inside the content embedded in the <iframe> — this includes things like downloads, form submissions, modals, and scripting. Note: See Third parties over on web.dev for additional useful information on auditing and more. Protect user data You need to make sure that user data is transmitted and stored securely once you've collected it. This is more of a security topic, but it is worth mentioning here — a good privacy policy is useless if your security is lax and attackers can steal the data from you. The below tips offer some guidance on protecting your user's data: Security is hard to get right. When implementing a secure solution that involves data collection — particularly if it is sensitive data such as sign-in credentials — it makes sense to use a reputable solution from a well-respected provider. For example, any respectable server-side framework will have built-in features to protect against common vulnerabilities. You could also consider using a specialized product for your purpose — for example an identity provider solution, or a secure online survey provider. If you want to roll out your own solution for collecting user data, make sure you understand what you are doing. Hire an experienced server-side developer and/or security engineer to implement the system, and ensure it is tested thoroughly. Use multi-factor authentication (MFA) to provide better protection. Consider using a dedicated API such as Web Authentication or Federated Credential Management to streamline the client-side of the app. When collecting user sign-up information, enforce strong passwords so your user's account details cannot be easily guessed. Weak passwords are one of the main causes of security breaches. Encourage your users to use a password manager to generate and store complex passwords; this way they won't worry about remembering them, or create a security risk by writing them down. Don't include sensitive data in URLs — if a third party intercepts the URL (for example via the Referer header), they could steal that information. Use POST requests rather than GET requests to avoid this. Consider using tools like Content Security Policy and Permissions Policy to enforce a set of feature usage on your site that makes it harder to introduce vulnerabilities. Be careful when doing this — if you block usage of a feature that a third-party script relies on to work, you may end up breaking your site's functionality. This is something you can look into when auditing your third-party resources (see Carefully manage third-party resources ). See also Web security Learn Privacy on web.dev Lean Data Practices on mozilla.org Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 3, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Privacy Guides Firefox tracking protection Privacy sandbox CHIPS Enrollment Bounce tracking mitigations Redirect tracking protection State Partitioning Referer header: Privacy and security concerns Storage access policy Errors Blocked: All storage access requests Blocked: All third-party storage access requests Blocked: Custom cookie permission Blocked: Storage access requests from trackers Partitioned: All third-party storage access requests Third-party cookies Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Working_with_objects | Working with objects - JavaScript | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web JavaScript Guide Working with objects Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) Working with objects Previous Next JavaScript is designed on an object-based paradigm. An object is a collection of properties , and a property is an association between a name (or key ) and a value. A property's value can be a function, in which case the property is known as a method . Objects in JavaScript, just as in many other programming languages, can be compared to objects in real life. In JavaScript, an object is a standalone entity, with properties and type. Compare it with a cup, for example. A cup is an object with properties. A cup has a color, a design, weight, a material it is made of, etc. In the same way, JavaScript objects can have properties, which define their characteristics. In addition to objects that are predefined in the browser, you can define your own objects. This chapter describes how to use objects, properties, and methods, and how to create your own objects. In this article Creating new objects Objects and properties Inheritance Defining methods Defining getters and setters Comparing objects See also Creating new objects You can create an object using an object initializer . Alternatively, you can first create a constructor function and then instantiate an object by invoking that function with the new operator. Using object initializers Object initializers are also called object literals . "Object initializer" is consistent with the terminology used by C++. The syntax for an object using an object initializer is: js const obj = { property1: value1, // property name may be an identifier 2: value2, // or a number "property n": value3, // or a string }; Each property name before colons is an identifier (either a name, a number, or a string literal), and each valueN is an expression whose value is assigned to the property name. The property name can also be an expression; computed keys need to be wrapped in square brackets. The object initializer reference contains a more detailed explanation of the syntax. In this example, the newly created object is assigned to a variable obj — this is optional. If you do not need to refer to this object elsewhere, you do not need to assign it to a variable. (Note that you may need to wrap the object literal in parentheses if the object appears where a statement is expected, so as not to have the literal be confused with a block statement.) Object initializers are expressions, and each object initializer results in a new object being created whenever the statement in which it appears is executed. Identical object initializers create distinct objects that do not compare to each other as equal. The following statement creates an object and assigns it to the variable x if and only if the expression cond is true: js let x; if (cond) { x = { greeting: "hi there" }; } The following example creates myHonda with three properties. Note that the engine property is also an object with its own properties. js const myHonda = { color: "red", wheels: 4, engine: { cylinders: 4, size: 2.2 }, }; Objects created with initializers are called plain objects , because they are instances of Object , but not any other object type. Some object types have special initializer syntaxes — for example, array initializers and regex literals . Using a constructor function Alternatively, you can create an object with these two steps: Define the object type by writing a constructor function. There is a strong convention, with good reason, to use a capital initial letter. Create an instance of the object with new . To define an object type, create a function for the object type that specifies its name, properties, and methods. For example, suppose you want to create an object type for cars. You want this type of object to be called Car , and you want it to have properties for make, model, and year. To do this, you would write the following function: js function Car(make, model, year) { this.make = make; this.model = model; this.year = year; } Notice the use of this to assign values to the object's properties based on the values passed to the function. Now you can create an object called myCar as follows: js const myCar = new Car("Eagle", "Talon TSi", 1993); This statement creates myCar and assigns it the specified values for its properties. Then the value of myCar.make is the string "Eagle" , myCar.model is the string "Talon TSi" , myCar.year is the integer 1993 , and so on. The order of arguments and parameters should be the same. You can create any number of Car objects by calls to new . For example, js const randCar = new Car("Nissan", "300ZX", 1992); const kenCar = new Car("Mazda", "Miata", 1990); An object can have a property that is itself another object. For example, suppose you define an object called Person as follows: js function Person(name, age, sex) { this.name = name; this.age = age; this.sex = sex; } and then instantiate two new Person objects as follows: js const rand = new Person("Rand McKinnon", 33, "M"); const ken = new Person("Ken Jones", 39, "M"); Then, you can rewrite the definition of Car to include an owner property that takes a Person object, as follows: js function Car(make, model, year, owner) { this.make = make; this.model = model; this.year = year; this.owner = owner; } To instantiate the new objects, you then use the following: js const car1 = new Car("Eagle", "Talon TSi", 1993, rand); const car2 = new Car("Nissan", "300ZX", 1992, ken); Notice that instead of passing a literal string or integer value when creating the new objects, the above statements pass the objects rand and ken as the arguments for the owners. Then if you want to find out the name of the owner of car2 , you can access the following property: js car2.owner.name; You can always add a property to a previously defined object. For example, the statement js car1.color = "black"; adds a property color to car1 , and assigns it a value of "black" . However, this does not affect any other objects. To add the new property to all objects of the same type, you have to add the property to the definition of the Car object type. You can also use the class syntax instead of the function syntax to define a constructor function. For more information, see the class guide . Using the Object.create() method Objects can also be created using the Object.create() method. This method can be very useful, because it allows you to choose the prototype object for the object you want to create, without having to define a constructor function. js // Animal properties and method encapsulation const animalProto = { type: "Invertebrates", // Default value of properties displayType() { // Method which will display the type of animal console.log(this.type); }, }; // Create a new animal type called `animal` const animal = Object.create(animalProto); animal.displayType(); // Logs: Invertebrates // Create a new animal type called fish const fish = Object.create(animalProto); fish.type = "Fishes"; fish.displayType(); // Logs: Fishes Objects and properties A JavaScript object has properties associated with it. Object properties are basically the same as variables, except that they are associated with objects, not scopes . The properties of an object define the characteristics of the object. For example, this example creates an object named myCar , with properties named make , model , and year , with their values set to "Ford" , "Mustang" , and 1969 : js const myCar = { make: "Ford", model: "Mustang", year: 1969, }; Like JavaScript variables, property names are case sensitive. Property names can only be strings or Symbols — all keys are converted to strings unless they are Symbols. Array indices are, in fact, properties with string keys that contain integers. Accessing properties You can access a property of an object by its property name. Property accessors come in two syntaxes: dot notation and bracket notation . For example, you could access the properties of the myCar object as follows: js // Dot notation myCar.make = "Ford"; myCar.model = "Mustang"; myCar.year = 1969; // Bracket notation myCar["make"] = "Ford"; myCar["model"] = "Mustang"; myCar["year"] = 1969; An object property name can be any JavaScript string or symbol , including an empty string. However, you cannot use dot notation to access a property whose name is not a valid JavaScript identifier. For example, a property name that has a space or a hyphen, that starts with a number, or that is held inside a variable can only be accessed using the bracket notation. This notation is also very useful when property names are to be dynamically determined, i.e., not determinable until runtime. Examples are as follows: js const myObj = {}; const str = "myString"; const rand = Math.random(); const anotherObj = {}; // Create additional properties on myObj myObj.type = "Dot syntax for a key named type"; myObj["date created"] = "This key has a space"; myObj[str] = "This key is in variable str"; myObj[rand] = "A random number is the key here"; myObj[anotherObj] = "This key is object anotherObj"; myObj[""] = "This key is an empty string"; console.log(myObj); // { // type: 'Dot syntax for a key named type', // 'date created': 'This key has a space', // myString: 'This key is in variable str', // '0.6398914448618778': 'A random number is the key here', // '[object Object]': 'This key is object anotherObj', // '': 'This key is an empty string' // } console.log(myObj.myString); // 'This key is in variable str' In the above code, the key anotherObj is an object, which is neither a string nor a symbol. When it is added to the myObj , JavaScript calls the toString() method of anotherObj , and use the resulting string as the new key. You can also access properties with a string value stored in a variable. The variable must be passed in bracket notation. In the example above, the variable str held "myString" and it is "myString" that is the property name. Therefore, myObj.str will return as undefined. js str = "myString"; myObj[str] = "This key is in variable str"; console.log(myObj.str); // undefined console.log(myObj[str]); // 'This key is in variable str' console.log(myObj.myString); // 'This key is in variable str' This allows accessing any property as determined at runtime: js let propertyName = "make"; myCar[propertyName] = "Ford"; // access different properties by changing the contents of the variable propertyName = "model"; myCar[propertyName] = "Mustang"; console.log(myCar); // { make: 'Ford', model: 'Mustang' } However, beware of using square brackets to access properties whose names are given by external input. This may make your code susceptible to object injection attacks . Nonexistent properties of an object have value undefined (and not null ). js myCar.nonexistentProperty; // undefined Enumerating properties There are three native ways to list/traverse object properties: for...in loops. This method traverses all of the enumerable string properties of an object as well as its prototype chain. Object.keys() . This method returns an array with only the enumerable own string property names ("keys") in the object myObj , but not those in the prototype chain. Object.getOwnPropertyNames() . This method returns an array containing all the own string property names in the object myObj , regardless of if they are enumerable or not. You can use the bracket notation with for...in to iterate over all the enumerable properties of an object. To illustrate how this works, the following function displays the properties of the object when you pass the object and the object's name as arguments to the function: js function showProps(obj, objName) { let result = ""; for (const i in obj) { // Object.hasOwn() is used to exclude properties from the object's // prototype chain and only show "own properties" if (Object.hasOwn(obj, i)) { result += `${objName}.${i} = ${obj[i]}\n`; } } console.log(result); } The term "own property" refers to the properties of the object, but excluding those of the prototype chain. So, the function call showProps(myCar, 'myCar') would print the following: myCar.make = Ford myCar.model = Mustang myCar.year = 1969 The above is equivalent to: js function showProps(obj, objName) { let result = ""; Object.keys(obj).forEach((i) => { result += `${objName}.${i} = ${obj[i]}\n`; }); console.log(result); } There is no native way to list all inherited properties, including non-enumerable ones. However, this can be achieved with the following function: js function listAllProperties(myObj) { let objectToInspect = myObj; let result = []; while (objectToInspect !== null) { result = result.concat(Object.getOwnPropertyNames(objectToInspect)); objectToInspect = Object.getPrototypeOf(objectToInspect); } return result; } For more information, see Enumerability and ownership of properties . Deleting properties You can remove a non-inherited property using the delete operator. The following code shows how to remove a property. js // Creates a new object, myObj, with two properties, a and b. const myObj = { a: 5, b: 12 }; // Removes the a property, leaving myObj with only the b property. delete myObj.a; console.log("a" in myObj); // false Inheritance All objects in JavaScript inherit from at least one other object. The object being inherited from is known as the prototype, and the inherited properties can be found in the prototype object of the constructor. See Inheritance and the prototype chain for more information. Defining properties for all objects of one type You can add a property to all objects created through a certain constructor using the prototype property. This defines a property that is shared by all objects of the specified type, rather than by just one instance of the object. The following code adds a color property to all objects of type Car , and then reads the property's value from an instance car1 . js Car.prototype.color = "red"; console.log(car1.color); // "red" Defining methods A method is a function associated with an object, or, put differently, a method is a property of an object that is a function. Methods are defined the way normal functions are defined, except that they have to be assigned as the property of an object. See also method definitions for more details. An example is: js objectName.methodName = functionName; const myObj = { myMethod: function (params) { // do something }, // this works too! myOtherMethod(params) { // do something else }, }; where objectName is an existing object, methodName is the name you are assigning to the method, and functionName is the name of the function. You can then call the method in the context of the object as follows: js objectName.methodName(params); Methods are typically defined on the prototype object of the constructor, so that all objects of the same type share the same method. For example, you can define a function that formats and displays the properties of the previously-defined Car objects. js Car.prototype.displayCar = function () { const result = `A Beautiful ${this.year} ${this.make} ${this.model}`; console.log(result); }; Notice the use of this to refer to the object to which the method belongs. Then you can call the displayCar method for each of the objects as follows: js car1.displayCar(); car2.displayCar(); Using this for object references JavaScript has a special keyword, this , that you can use within a method to refer to the current object. For example, suppose you have 2 objects, manager and intern . Each object has its own name , age and job . In the function sayHi() , notice the use of this.name . When added to the 2 objects, the same function will print the message with the name of the respective object it's attached to. js const manager = { name: "Karina", age: 27, job: "Software Engineer", }; const intern = { name: "Tyrone", age: 21, job: "Software Engineer Intern", }; function sayHi() { console.log(`Hello, my name is ${this.name}`); } // Add sayHi function to both objects manager.sayHi = sayHi; intern.sayHi = sayHi; manager.sayHi(); // Hello, my name is Karina intern.sayHi(); // Hello, my name is Tyrone this is a "hidden parameter" of a function call that's passed in by specifying the object before the function that was called. For example, in manager.sayHi() , this is the manager object, because manager comes before the function sayHi() . If you access the same function from another object, this will change as well. If you use other methods to call the function, like Function.prototype.call() or Reflect.apply() , you can explicitly pass the value of this as an argument. Defining getters and setters A getter is a function associated with a property that gets the value of a specific property. A setter is a function associated with a property that sets the value of a specific property. Together, they can indirectly represent the value of a property. Getters and setters can be either defined within object initializers , or added later to any existing object. Within object initializers , getters and setters are defined like regular methods , but prefixed with the keywords get or set . The getter method must not expect a parameter, while the setter method expects exactly one parameter (the new value to set). For instance: js const myObj = { a: 7, get b() { return this.a + 1; }, set c(x) { this.a = x / 2; }, }; console.log(myObj.a); // 7 console.log(myObj.b); // 8, returned from the get b() method myObj.c = 50; // Calls the set c(x) method console.log(myObj.a); // 25 The myObj object's properties are: myObj.a — a number myObj.b — a getter that returns myObj.a plus 1 myObj.c — a setter that sets the value of myObj.a to half of the value myObj.c is being set to Getters and setters can also be added to an object at any time after creation using the Object.defineProperties() method. This method's first parameter is the object on which you want to define the getter or setter. The second parameter is an object whose property names are the getter or setter names, and whose property values are objects for defining the getter or setter functions. Here's an example that defines the same getter and setter used in the previous example: js const myObj = { a: 0 }; Object.defineProperties(myObj, { b: { get() { return this.a + 1; }, }, c: { set(x) { this.a = x / 2; }, }, }); myObj.c = 10; // Runs the setter, which assigns 10 / 2 (5) to the 'a' property console.log(myObj.b); // Runs the getter, which yields a + 1 or 6 Which of the two forms to choose depends on your programming style and task at hand. If you can change the definition of the original object, you will probably define getters and setters through the original initializer. This form is more compact and natural. However, if you need to add getters and setters later — maybe because you did not write the particular object — then the second form is the only possible form. The second form better represents the dynamic nature of JavaScript, but it can make the code hard to read and understand. Comparing objects In JavaScript, objects are a reference type. Two distinct objects are never equal, even if they have the same properties. Only comparing the same object reference with itself yields true. js // Two variables, two distinct objects with the same properties const fruit = { name: "apple" }; const anotherFruit = { name: "apple" }; fruit == anotherFruit; // return false fruit === anotherFruit; // return false js // Two variables, a single object const fruit = { name: "apple" }; const anotherFruit = fruit; // Assign fruit object reference to anotherFruit // Here fruit and anotherFruit are pointing to same object fruit == anotherFruit; // return true fruit === anotherFruit; // return true fruit.name = "grape"; console.log(anotherFruit); // { name: "grape" }; not { name: "apple" } For more information about comparison operators, see equality operators . See also Inheritance and the prototype chain Classes Previous Next Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 17, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar JavaScript Tutorials and guides JavaScript Guide Introduction Grammar and types Control flow and error handling Loops and iteration Functions Expressions and operators Numbers and strings Representing dates & times Regular expressions Indexed collections Keyed collections Working with objects Using classes Using promises JavaScript typed arrays Iterators and generators Resource management Internationalization JavaScript modules Intermediate Language overview JavaScript data structures Equality comparisons and sameness Enumerability and ownership of properties Closures Advanced Inheritance and the prototype chain Meta programming Memory Management References Built-in objects AggregateError Array ArrayBuffer AsyncDisposableStack AsyncFunction AsyncGenerator AsyncGeneratorFunction AsyncIterator Atomics BigInt BigInt64Array BigUint64Array Boolean DataView Date decodeURI() decodeURIComponent() DisposableStack encodeURI() encodeURIComponent() Error escape() Deprecated eval() EvalError FinalizationRegistry Float16Array Float32Array Float64Array Function Generator GeneratorFunction globalThis Infinity Int8Array Int16Array Int32Array InternalError Non-standard Intl isFinite() isNaN() Iterator JSON Map Math NaN Number Object parseFloat() parseInt() Promise Proxy RangeError ReferenceError Reflect RegExp Set SharedArrayBuffer String SuppressedError Symbol SyntaxError Temporal TypedArray TypeError Uint8Array Uint8ClampedArray Uint16Array Uint32Array undefined unescape() Deprecated URIError WeakMap WeakRef WeakSet Expressions & operators Addition (+) Addition assignment (+=) Assignment (=) async function expression async function* expression await Bitwise AND (&) Bitwise AND assignment (&=) Bitwise NOT (~) Bitwise OR (|) Bitwise OR assignment (|=) Bitwise XOR (^) Bitwise XOR assignment (^=) class expression Comma operator (,) Conditional (ternary) operator Decrement (--) delete Destructuring Division (/) Division assignment (/=) Equality (==) Exponentiation (**) Exponentiation assignment (**=) function expression function* expression Greater than (>) Greater than or equal (>=) Grouping operator ( ) import.meta import.meta.resolve() import() in Increment (++) Inequality (!=) instanceof Left shift (<<) Left shift assignment (<<=) Less than (<) Less than or equal (<=) Logical AND (&&) Logical AND assignment (&&=) Logical NOT (!) Logical OR (||) Logical OR assignment (||=) Multiplication (*) Multiplication assignment (*=) new new.target null Nullish coalescing assignment (??=) Nullish coalescing operator (??) Object initializer Operator precedence Optional chaining (?.) Property accessors Remainder (%) Remainder assignment (%=) Right shift (>>) Right shift assignment (>>=) Spread syntax (...) Strict equality (===) Strict inequality (!==) Subtraction (-) Subtraction assignment (-=) super this typeof Unary negation (-) Unary plus (+) Unsigned right shift (>>>) Unsigned right shift assignment (>>>=) void operator yield yield* Statements & declarations async function async function* await using Block statement break class const continue debugger do...while Empty statement export Expression statement for for await...of for...in for...of function function* if...else import Import attributes Labeled statement let return switch throw try...catch using var while with Deprecated Functions Arrow function expressions Default parameters get Method definitions Rest parameters set The arguments object [Symbol.iterator]() callee Deprecated length Classes constructor extends Private elements Public class fields static Static initialization blocks Regular expressions Backreference: \1, \2 Capturing group: (...) Character class escape: \d, \D, \w, \W, \s, \S Character class: [...], [^...] Character escape: \n, \u{...} Disjunction: | Input boundary assertion: ^, $ Literal character: a, b Lookahead assertion: (?=...), (?!...) Lookbehind assertion: (?<=...), (?<!...) Modifier: (?ims-ims:...) Named backreference: \k<name> Named capturing group: (?<name>...) Non-capturing group: (?:...) Quantifier: *, +, ?, {n}, {n,}, {n,m} Unicode character class escape: \p{...}, \P{...} Wildcard: . Word boundary assertion: \b, \B Errors AggregateError: No Promise in Promise.any was resolved Error: Permission denied to access property "x" InternalError: too much recursion RangeError: argument is not a valid code point RangeError: BigInt division by zero RangeError: BigInt negative exponent RangeError: form must be one of 'NFC', 'NFD', 'NFKC', or 'NFKD' RangeError: invalid array length RangeError: invalid date RangeError: precision is out of range RangeError: radix must be an integer RangeError: repeat count must be less than infinity RangeError: repeat count must be non-negative RangeError: x can't be converted to BigInt because it isn't an integer ReferenceError: "x" is not defined ReferenceError: assignment to undeclared variable "x" ReferenceError: can't access lexical declaration 'X' before initialization ReferenceError: must call super constructor before using 'this' in derived class constructor ReferenceError: super() called twice in derived class constructor SyntaxError: 'arguments'/'eval' can't be defined or assigned to in strict mode code SyntaxError: "0"-prefixed octal literals are deprecated SyntaxError: "use strict" not allowed in function with non-simple parameters SyntaxError: "x" is a reserved identifier SyntaxError: \ at end of pattern SyntaxError: a declaration in the head of a for-of loop can't have an initializer SyntaxError: applying the 'delete' operator to an unqualified name is deprecated SyntaxError: arguments is not valid in fields SyntaxError: await is only valid in async functions, async generators and modules SyntaxError: await/yield expression can't be used in parameter SyntaxError: cannot use `??` unparenthesized within `||` and `&&` expressions SyntaxError: character class escape cannot be used in class range in regular expression SyntaxError: continue must be inside loop SyntaxError: duplicate capture group name in regular expression SyntaxError: duplicate formal argument x SyntaxError: for-in loop head declarations may not have initializers SyntaxError: function statement requires a name SyntaxError: functions cannot be labelled SyntaxError: getter and setter for private name #x should either be both static or non-static SyntaxError: getter functions must have no arguments SyntaxError: identifier starts immediately after numeric literal SyntaxError: illegal character SyntaxError: import declarations may only appear at top level of a module SyntaxError: incomplete quantifier in regular expression SyntaxError: invalid assignment left-hand side SyntaxError: invalid BigInt syntax SyntaxError: invalid capture group name in regular expression SyntaxError: invalid character in class in regular expression SyntaxError: invalid class set operation in regular expression SyntaxError: invalid decimal escape in regular expression SyntaxError: invalid identity escape in regular expression SyntaxError: invalid named capture reference in regular expression SyntaxError: invalid property name in regular expression SyntaxError: invalid range in character class SyntaxError: invalid regexp group SyntaxError: invalid regular expression flag "x" SyntaxError: invalid unicode escape in regular expression SyntaxError: JSON.parse: bad parsing SyntaxError: label not found SyntaxError: missing : after property id SyntaxError: missing ) after argument list SyntaxError: missing ) after condition SyntaxError: missing ] after element list SyntaxError: missing } after function body SyntaxError: missing } after property list SyntaxError: missing = in const declaration SyntaxError: missing formal parameter SyntaxError: missing name after . operator SyntaxError: missing variable name SyntaxError: negated character class with strings in regular expression SyntaxError: new keyword cannot be used with an optional chain SyntaxError: nothing to repeat SyntaxError: numbers out of order in {} quantifier. SyntaxError: octal escape sequences can't be used in untagged template literals or in strict mode code SyntaxError: parameter after rest parameter SyntaxError: private fields can't be deleted SyntaxError: property name __proto__ appears more than once in object literal SyntaxError: raw bracket is not allowed in regular expression with unicode flag SyntaxError: redeclaration of formal parameter "x" SyntaxError: reference to undeclared private field or method #x SyntaxError: rest parameter may not have a default SyntaxError: return not in function SyntaxError: setter functions must have one argument SyntaxError: string literal contains an unescaped line break SyntaxError: super() is only valid in derived class constructors SyntaxError: tagged template cannot be used with optional chain SyntaxError: Unexpected '#' used outside of class body SyntaxError: Unexpected token SyntaxError: unlabeled break must be inside loop or switch SyntaxError: unparenthesized unary expression can't appear on the left-hand side of '**' SyntaxError: use of super property/member accesses only valid within methods or eval code within methods SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed TypeError: 'x' is not iterable TypeError: "x" is (not) "y" TypeError: "x" is not a constructor TypeError: "x" is not a function TypeError: "x" is not a non-null object TypeError: "x" is read-only TypeError: already executing generator TypeError: BigInt value can't be serialized in JSON TypeError: calling a builtin X constructor without new is forbidden TypeError: can't access/set private field or method: object is not the right class TypeError: can't assign to property "x" on "y": not an object TypeError: can't convert BigInt to number TypeError: can't convert x to BigInt TypeError: can't define property "x": "obj" is not extensible TypeError: can't delete non-configurable array element TypeError: can't redefine non-configurable property "x" TypeError: can't set prototype of this object TypeError: can't set prototype: it would cause a prototype chain cycle TypeError: cannot use 'in' operator to search for 'x' in 'y' TypeError: class constructors must be invoked with 'new' TypeError: cyclic object value TypeError: derived class constructor returned invalid value x TypeError: getting private setter-only property TypeError: Initializing an object twice is an error with private fields/methods TypeError: invalid 'instanceof' operand 'x' TypeError: invalid Array.prototype.sort argument TypeError: invalid assignment to const "x" TypeError: Iterator/AsyncIterator constructor can't be used directly TypeError: matchAll/replaceAll must be called with a global RegExp TypeError: More arguments needed TypeError: null/undefined has no properties TypeError: property "x" is non-configurable and can't be deleted TypeError: Reduce of empty array with no initial value TypeError: setting getter-only property "x" TypeError: WeakSet key/WeakMap value 'x' must be an object or an unregistered symbol TypeError: X.prototype.y called on incompatible type URIError: malformed URI sequence Warning: -file- is being assigned a //# sourceMappingURL, but already has one Warning: unreachable code after return statement Misc JavaScript technologies overview Execution model Lexical grammar Iteration protocols Strict mode Template literals Trailing commas Deprecated features Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/CSS/How_to/Layout_cookbook/Column_layouts | Column layouts - CSS | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web CSS How to Layout cookbook Column layouts Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 中文 (简体) Column layouts You will often need to create a layout which has a number of columns, and CSS provides several ways to do this. Whether you use Multi-column , Flexbox , or Grid layout will depend on what you are trying to achieve, and in this recipe we explore these options. In this article Requirements The recipes Resources on MDN Requirements There are a number of design patterns you might want to achieve with your columns: A continuous thread of content broken up into newspaper-style columns . A single row of items arranged as columns, with all heights being equal . Multiple rows of columns lined up by row and column . The recipes You need to choose different layout methods in order to achieve your requirements. A continuous thread of content — multi-column layout If you create columns using multi-column layout your text will remain as a continuous stream filling each column in turn. The columns must all be the same size, and you are unable to target an individual column or the content of an individual column. You can control the gaps between columns with the column-gap or gap properties, and add a rule between columns using column-rule . Click "Play" in the code blocks below to edit the example in the MDN Playground: html <div class="container"> <p> Veggies es bonus vobis, proinde vos postulo essum magis kohlrabi welsh onion daikon amaranth tatsoi tomatillo melon azuki bean garlic. </p> <p> Gumbo beet greens corn soko endive gumbo gourd. Parsley shallot courgette tatsoi pea sprouts fava bean collard greens dandelion okra wakame tomato. Dandelion cucumber earthnut pea peanut soko zucchini. </p> <p> Turnip greens yarrow ricebean rutabaga endive cauliflower sea lettuce kohlrabi amaranth water spinach avocado daikon napa cabbage asparagus winter purslane kale. Celery potato scallion desert raisin horseradish spinach </p> </div> css .container { border: 2px solid rgb(75 70 74); border-radius: 0.5em; padding: 20px; font: 1.2em sans-serif; column-width: 10em; column-rule: 1px solid rgb(75 70 74); } In this example, we used the column-width property to set a minimum width that the columns need to be before the browser adds an additional column. The columns shorthand property can be used to set the column-width and column-count properties, either of which can define the maximum number of columns allowed. Use multicol when: You want your text to display in newspaper-like columns. You have a set of small items you want to break into columns. You do not need to target individual column boxes for styling. A single row of items with equal heights — flexbox Flexbox can be used to break content into columns by setting display: flex; to make a parent element a flex-container. Just adding this one property turns all the children (child elements, pseudo-elements, and text nodes) into flex items along a single line. Setting the same flex shorthand property with a single numeric value distributes all the available space equally, generally making all the flex items the same size as long as none have non-wrapping content forcing the item to be larger. Margins or the gap property can be used to create gaps between items, but there is currently no CSS property that adds rules between flex items. html <div class="container"> <p> Veggies es bonus vobis, proinde vos postulo essum magis kohlrabi welsh onion daikon amaranth tatsoi tomatillo melon azuki bean garlic. </p> <p> Gumbo beet greens corn soko endive gumbo gourd. Parsley shallot courgette tatsoi pea sprouts fava bean collard greens dandelion okra wakame tomato. Dandelion cucumber earthnut pea peanut soko zucchini. </p> <p> Turnip greens yarrow ricebean rutabaga endive cauliflower sea lettuce kohlrabi amaranth water spinach avocado daikon napa cabbage asparagus winter purslane kale. Celery potato scallion desert raisin horseradish spinach carrot soko. </p> </div> css .container { border: 2px solid rgb(75 70 74); border-radius: 0.5em; padding: 20px 10px; font: 1.2em sans-serif; display: flex; } .container > * { padding: 10px; border: 2px solid rgb(95 97 110); border-radius: 0.5em; margin: 0 10px; flex: 1; } To create a layout with flex items that wrap onto new rows, set the flex-wrap property on the container to wrap . Note that each flex line distributes space for that line only. Items in one line will not necessarily line up with items on other lines, as you'll see in the example below. This is why flexbox is described as one-dimensional. It is designed for controlling layout as a row or a column, but not both at the same time. html <div class="container"> <p> Veggies es bonus vobis, proinde vos postulo essum magis kohlrabi welsh onion daikon amaranth tatsoi tomatillo melon azuki bean garlic. </p> <p> Gumbo beet greens corn soko endive gumbo gourd. Parsley shallot courgette tatsoi pea sprouts fava bean collard greens dandelion okra wakame tomato. Dandelion cucumber earthnut pea peanut soko zucchini. </p> <p> Turnip greens yarrow ricebean rutabaga endive cauliflower sea lettuce kohlrabi amaranth water spinach avocado daikon napa cabbage asparagus winter purslane kale. Celery potato scallion desert raisin horseradish spinach carrot soko. </p> </div> css .container { border: 2px solid rgb(75 70 74); border-radius: 0.5em; padding: 20px 10px; width: 500px; font: 1.2em sans-serif; display: flex; flex-wrap: wrap; } .container > * { padding: 10px; border: 2px solid rgb(95 97 110); border-radius: 0.5em; margin: 0 10px; flex: 1 1 200px; } Use flexbox: For single rows or columns of items. When you want to do alignment on the cross axis after laying out your items. When you are happy for wrapped items to share out space along their line only and not line up with items in other lines. Lining items up in rows and columns — grid layout If you want a two-dimensional grid where items line up in rows and columns, then you should choose CSS grid layout. Similar to how flexbox works on the direct children of the flex container, grid layout works on the direct children of the grid container. Just set display: grid; on the container. Properties set on this container — like grid-template-columns and grid-template-rows — define how the items are distributed along rows and columns. Click "Play" in the code blocks below to edit the example in the MDN Playground: html <div class="container"> <p> Veggies es bonus vobis, proinde vos postulo essum magis kohlrabi welsh onion daikon amaranth tatsoi. </p> <p> Gumbo beet greens corn soko endive gumbo gourd. Parsley shallot courgette tatsoi pea sprouts fava bean collard greens. </p> <p> Nori grape silver beet broccoli kombu beet greens fava bean potato quandong celery. Bunya nuts black-eyed pea prairie turnip leek lentil turnip greens parsnip. . </p> </div> css .container { border: 2px solid rgb(75 70 74); border-radius: 0.5em; padding: 20px; width: 500px; font: 1.2em sans-serif; display: grid; grid-template-columns: 1fr 1fr; grid-gap: 20px; } .container > * { padding: 10px; border: 2px solid rgb(95 97 110); border-radius: 0.5em; margin: 0; } Use grid: For multiple rows or columns of items. When you want to be able to align the items on the block and inline axes. When you want items to line up in rows and columns. Resources on MDN Guide to Multi-column Layout Guide to flexbox Guide to CSS grid layout Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 7, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar CSS Guides Modules Anchor positioning Animations Backgrounds and borders Basic user interface Borders and box decorations Box alignment Box model Box sizing Cascading and inheritance Color adjustment Colors Compositing and blending Conditional rules Containment Counter styles CSSOM view Custom functions and mixins Custom highlight API Custom properties for cascading variables Display Easing functions Environment variables Filter effects Flexible box layout Font loading Fonts Fragmentation Generated content Grid layout Images Inline layout Lists and counters Logical properties and values Masking Media queries Motion path Multi-column layout Namespaces Nesting Overflow Overscroll behavior Paged media Positioned layout Properties and values API Pseudo-elements Round display Ruby layout Scoping Scroll anchoring Scroll snap Scroll-driven animations Scrollbars styling Selectors Shadow parts Shapes Syntax Table Text Text decoration Transforms Transitions Values and units View transitions Viewport Writing modes Anchor positioning Using anchor positioning Handling overflow Animations Animatable properties Using animations Backgrounds and borders Using multiple backgrounds Resizing background images Scaling SVG backgrounds Box alignment Overview In block layout In flexbox In grid layout In multi-column layout Box model Introduction Margin collapsing Box sizing Aspect ratios Cascade Introduction Inheritance Specificity Property value processing Shorthand properties Cascading variables Using custom properties Colors Applying color Color values Using relative colors Using color wisely Accessibility: Colors and luminance Accessibility: Color contrast Columns Basic concepts Styling columns Using multi-column layouts Spanning and balancing columns Handling overflow Handling content breaks Conditional rules Using feature queries Using container scroll-state queries Containment Container queries Using containment Using container size and style queries CSSOM view Coordinate systems (API) Viewport concepts Custom functions and mixins Using CSS custom functions Display Block and inline layout Flow layout Flow layout and overflow Flow layout and writing modes In flow and out of flow Layout and the containing block Formatting contexts Block formatting context Inline formatting context Using multi-keyword syntax Visual formatting model Environment variables Using environment variables Filter effects Using filter effects Flexbox Basic concepts Flexbox and other layouts Aligning flex items Ordering flex items Controlling flex item ratios Wrapping flex items Typical use cases Fonts OpenType features Variable fonts WOFF Grid Basic concepts Grid and other layouts Using line-based placement Grid template areas Using named grid lines Using auto-placement Aligning items Logical values and writing modes Grid layout and accessibility Common grid layouts Subgrid Masonry layout Experimental Images Using gradients Using object-view-box Styling replaced elements Implementing image sprites Lists and counters Using counters Indenting lists Logical properties Basic concepts For floating and positioning For margins, borders, and padding For sizing Masking Introduction Clipping Multiple masks Mask properties Media queries Using media queries For accessibility Testing Printing Nesting style rules Nesting at-rules Nesting and specificity Using nesting Overflow Creating carousels Positioning Stacking context Example 1 Example 2 Example 3 Stacking floating elements Understanding z-index Using z-index Stacking without z-index Scroll anchoring Overview Scroll-driven animations Scroll-driven animation timelines Scroll snap Basic concepts Using scroll snap events Selectors Selectors and combinators Selector structure Privacy and :visited Using :target Shapes Overview Box-value shapes Image-based shapes Using shape-outside Syntax Introduction Comments At-rules Error handling Text Wrapping and breaking text Handling whitespace Text decoration Text shadows Transforms Using transforms Transitions Using transitions Values and units Value definition syntax Numeric data types Textual data types Using math functions Using typed arithmetic Writing modes Introduction Vertical form controls How to Layout cookbook Media objects Column layouts Center an element Sticky footers Split navigation Breadcrumb navigation List group with badges Pagination Card Grid wrapper Contribute a recipe Cookbook template Tools Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator Reference Properties -moz-* -moz-float-edge Non-standard Deprecated -moz-force-broken-image-icon Non-standard Deprecated -moz-orient Non-standard -moz-user-focus Non-standard Deprecated -moz-user-input Non-standard Deprecated -webkit-* -webkit-border-before Non-standard -webkit-box-reflect Non-standard -webkit-mask-box-image Non-standard -webkit-mask-composite Non-standard -webkit-mask-position-x Non-standard -webkit-mask-position-y Non-standard -webkit-mask-repeat-x Non-standard -webkit-mask-repeat-y Non-standard -webkit-tap-highlight-color Non-standard -webkit-text-fill-color -webkit-text-security Non-standard -webkit-text-stroke -webkit-text-stroke-color -webkit-text-stroke-width -webkit-touch-callout Non-standard Custom properties (--*): CSS variables accent-color align-* align-content align-items align-self alignment-baseline all anchor-name anchor-scope animation-* animation animation-composition animation-delay animation-direction animation-duration animation-fill-mode animation-iteration-count animation-name animation-play-state animation-range animation-range-end animation-range-start animation-timeline animation-timing-function appearance aspect-ratio backdrop-filter backface-visibility background-* background background-attachment background-blend-mode background-clip background-color background-image background-origin background-position background-position-x background-position-y background-repeat background-size baseline-source block-size border-* border border-block border-block-color border-block-end border-block-end-color border-block-end-style border-block-end-width border-block-start border-block-start-color border-block-start-style border-block-start-width border-block-style border-block-width border-bottom border-bottom-color border-bottom-left-radius border-bottom-right-radius border-bottom-style border-bottom-width border-collapse border-color border-end-end-radius border-end-start-radius border-image border-image-outset border-image-repeat border-image-slice border-image-source border-image-width border-inline border-inline-color border-inline-end border-inline-end-color border-inline-end-style border-inline-end-width border-inline-start border-inline-start-color border-inline-start-style border-inline-start-width border-inline-style border-inline-width border-left border-left-color border-left-style border-left-width border-radius border-right border-right-color border-right-style border-right-width border-spacing border-start-end-radius border-start-start-radius border-style border-top border-top-color border-top-left-radius border-top-right-radius border-top-style border-top-width border-width bottom box-* box-align Non-standard Deprecated box-decoration-break box-direction Non-standard Deprecated box-flex Non-standard Deprecated box-flex-group Non-standard Deprecated box-lines Non-standard Deprecated box-ordinal-group Non-standard Deprecated box-orient Non-standard Deprecated box-pack Non-standard Deprecated box-shadow box-sizing break-* break-after break-before break-inside caption-side caret-* caret Experimental caret-animation Experimental caret-color caret-shape Experimental clear clip-* clip Deprecated clip-path clip-rule color-* color color-interpolation color-interpolation-filters color-scheme column-* column-count column-fill column-gap column-rule column-rule-color column-rule-style column-rule-width column-span column-width columns contain-* contain contain-intrinsic-block-size contain-intrinsic-height contain-intrinsic-inline-size contain-intrinsic-size contain-intrinsic-width container-* container container-name container-type content content-visibility corner-* corner-block-end-shape Experimental corner-block-start-shape Experimental corner-bottom-left-shape Experimental corner-bottom-right-shape Experimental corner-bottom-shape Experimental corner-end-end-shape Experimental corner-end-start-shape Experimental corner-inline-end-shape Experimental corner-inline-start-shape Experimental corner-left-shape Experimental corner-right-shape Experimental corner-shape Experimental corner-start-end-shape Experimental corner-start-start-shape Experimental corner-top-left-shape Experimental corner-top-right-shape Experimental corner-top-shape Experimental counter-* counter-increment counter-reset counter-set cursor cx cy d direction display dominant-baseline dynamic-range-limit empty-cells field-sizing fill-* fill fill-opacity fill-rule filter flex-* flex flex-basis flex-direction flex-flow flex-grow flex-shrink flex-wrap float flood-color flood-opacity font-* font font-family font-feature-settings font-kerning font-language-override font-optical-sizing font-palette font-size font-size-adjust font-smooth Non-standard font-stretch Deprecated font-style font-synthesis font-synthesis-position Experimental font-synthesis-small-caps font-synthesis-style font-synthesis-weight font-variant font-variant-alternates font-variant-caps font-variant-east-asian font-variant-emoji font-variant-ligatures font-variant-numeric font-variant-position font-variation-settings font-weight forced-color-adjust gap grid-* grid grid-area grid-auto-columns grid-auto-flow grid-auto-rows grid-column grid-column-end grid-column-start grid-row grid-row-end grid-row-start grid-template grid-template-areas grid-template-columns grid-template-rows hanging-punctuation height hyphenate-character hyphenate-limit-chars hyphens image-* image-orientation image-rendering image-resolution Experimental initial-letter inline-size inset-* inset inset-block inset-block-end inset-block-start inset-inline inset-inline-end inset-inline-start interactivity Experimental interest-* interest-delay Experimental interest-delay-end Experimental interest-delay-start Experimental interpolate-size Experimental isolation justify-* justify-content justify-items justify-self left letter-spacing lighting-color line-* line-break line-clamp line-height line-height-step Experimental list-* list-style list-style-image list-style-position list-style-type margin-* margin margin-block margin-block-end margin-block-start margin-bottom margin-inline margin-inline-end margin-inline-start margin-left margin-right margin-top margin-trim Experimental marker-* marker marker-end marker-mid marker-start mask-* mask mask-border mask-border-mode mask-border-outset mask-border-repeat mask-border-slice mask-border-source mask-border-width mask-clip mask-composite mask-image mask-mode mask-origin mask-position mask-repeat mask-size mask-type math-* math-depth math-shift math-style max-* max-block-size max-height max-inline-size max-width min-* min-block-size min-height min-inline-size min-width mix-blend-mode object-* object-fit object-position object-view-box Experimental offset-* offset offset-anchor offset-distance offset-path offset-position offset-rotate opacity order orphans outline-* outline outline-color outline-offset outline-style outline-width overflow-* overflow overflow-anchor overflow-block overflow-clip-margin overflow-inline overflow-wrap overflow-x overflow-y overlay Experimental overscroll-* overscroll-behavior overscroll-behavior-block overscroll-behavior-inline overscroll-behavior-x overscroll-behavior-y padding-* padding padding-block padding-block-end padding-block-start padding-bottom padding-inline padding-inline-end padding-inline-start padding-left padding-right padding-top page-* page page-break-after Deprecated page-break-before Deprecated page-break-inside Deprecated paint-order perspective perspective-origin place-* place-content place-items place-self pointer-events position-* position position-anchor position-area position-try position-try-fallbacks position-try-order position-visibility print-color-adjust quotes r reading-flow Experimental reading-order Experimental resize right rotate row-gap ruby-* ruby-align ruby-overhang ruby-position rx ry scale scroll-* scroll-behavior scroll-margin scroll-margin-block scroll-margin-block-end scroll-margin-block-start scroll-margin-bottom scroll-margin-inline scroll-margin-inline-end scroll-margin-inline-start scroll-margin-left scroll-margin-right scroll-margin-top scroll-marker-group Experimental scroll-padding scroll-padding-block scroll-padding-block-end scroll-padding-block-start scroll-padding-bottom scroll-padding-inline scroll-padding-inline-end scroll-padding-inline-start scroll-padding-left scroll-padding-right scroll-padding-top scroll-snap-align scroll-snap-stop scroll-snap-type scroll-target-group Experimental scroll-timeline scroll-timeline-axis scroll-timeline-name scrollbar-* scrollbar-color scrollbar-gutter scrollbar-width shape-* shape-image-threshold shape-margin shape-outside shape-rendering speak-as Experimental stop-color stop-opacity stroke-* stroke stroke-dasharray stroke-dashoffset stroke-linecap stroke-linejoin stroke-miterlimit stroke-opacity stroke-width tab-size table-layout text-* text-align text-align-last text-anchor text-autospace text-box text-box-edge text-box-trim text-combine-upright text-decoration text-decoration-color text-decoration-inset Experimental text-decoration-line text-decoration-skip Experimental text-decoration-skip-ink text-decoration-style text-decoration-thickness text-emphasis text-emphasis-color text-emphasis-position text-emphasis-style text-indent text-justify text-orientation text-overflow text-rendering text-shadow text-size-adjust Experimental text-spacing-trim Experimental text-transform text-underline-offset text-underline-position text-wrap text-wrap-mode text-wrap-style timeline-scope top touch-action transform-* transform transform-box transform-origin transform-style transition-* transition transition-behavior transition-delay transition-duration transition-property transition-timing-function translate unicode-bidi user-modify Non-standard Deprecated user-select vector-effect vertical-align view-* view-timeline view-timeline-axis view-timeline-inset view-timeline-name view-transition-class view-transition-name visibility white-space white-space-collapse widows width will-change word-break word-spacing writing-mode x y z-index zoom Selectors & nesting selector Attribute selectors Class selectors ID selectors Keyframe selectors Namespace separator Selector list Type selectors Universal selectors Combinators Child combinator Column combinator Experimental Descendant combinator Next-sibling combinator Subsequent-sibling combinator Pseudo-classes :-moz-* :-moz-broken Non-standard Deprecated :-moz-drag-over Non-standard :-moz-first-node Experimental Non-standard :-moz-handler-blocked Non-standard :-moz-handler-crashed Non-standard :-moz-handler-disabled Non-standard :-moz-last-node Experimental Non-standard :-moz-loading Non-standard :-moz-locale-dir(ltr) Non-standard :-moz-locale-dir(rtl) Non-standard :-moz-only-whitespace Non-standard :-moz-submit-invalid Non-standard :-moz-suppressed Non-standard :-moz-user-disabled Non-standard :-moz-window-inactive Non-standard :active-* :active :active-view-transition :active-view-transition-type() :any-link :autofill :blank Experimental :buffering :checked :current Experimental :default :defined :dir() :disabled :empty :enabled :first-* :first :first-child :first-of-type :focus-* :focus :focus-visible :focus-within :fullscreen :future :has-slotted :has() :heading Experimental :heading() Experimental :host :host-context() Deprecated :host() :hover :in-range :indeterminate :interest-source Experimental :interest-target Experimental :invalid :is() :lang() :last-child :last-of-type :left :link :local-link Experimental :modal :muted :not() :nth-* :nth-child() :nth-last-child() :nth-last-of-type() :nth-of-type() :only-child :only-of-type :open :optional :out-of-range :past :paused :picture-in-picture :placeholder-shown :playing :popover-open :read-only :read-write :required :right :root :scope :seeking :stalled :state() :target-* :target :target-after Experimental :target-before Experimental :target-current Experimental :user-invalid :user-valid :valid :visited :volume-locked :where() Pseudo-elements ::-moz-* ::-moz-color-swatch Non-standard ::-moz-focus-inner Non-standard Deprecated ::-moz-list-bullet Experimental Non-standard ::-moz-list-number Experimental Non-standard ::-moz-meter-bar Non-standard ::-moz-progress-bar Experimental Non-standard ::-moz-range-progress Non-standard ::-moz-range-thumb Non-standard ::-moz-range-track Non-standard ::-webkit-* ::-webkit-inner-spin-button Non-standard ::-webkit-meter-bar Non-standard Deprecated ::-webkit-meter-even-less-good-value Non-standard ::-webkit-meter-inner-element Non-standard ::-webkit-meter-optimum-value Non-standard ::-webkit-meter-suboptimum-value Non-standard ::-webkit-progress-bar Non-standard ::-webkit-progress-inner-element Non-standard ::-webkit-progress-value Non-standard ::-webkit-scrollbar Non-standard ::-webkit-search-cancel-button Non-standard ::-webkit-search-results-button Non-standard ::-webkit-slider-runnable-track Non-standard ::-webkit-slider-thumb Non-standard ::after ::backdrop ::before ::checkmark Experimental ::column Experimental ::cue ::details-content ::file-selector-button ::first-letter ::first-line ::grammar-error ::highlight() ::marker ::part() ::picker-icon Experimental ::picker() Experimental ::placeholder ::scroll-* ::scroll-button() Experimental ::scroll-marker Experimental ::scroll-marker-group Experimental ::selection ::slotted() ::spelling-error ::target-text ::view-* ::view-transition ::view-transition-group() ::view-transition-image-pair() ::view-transition-new() ::view-transition-old() At-rules @charset @color-profile @container @counter-style @custom-media Experimental @document Non-standard Deprecated @font-face @font-feature-values @font-palette-values @function Experimental @import @keyframes @layer @media @namespace @page @position-try @property @scope @starting-style @supports @view-transition Values !important fit-content inherit initial max-content min-content revert revert-layer rule-list unset Types <absolute-size> <alpha-value> <angle-percentage> <angle> <axis> <baseline-position> <basic-shape> <blend-mode> <box-edge> <calc-keyword> <calc-sum> <color-interpolation-method> <color> <content-distribution> <content-position> <corner-shape-value> Experimental <custom-ident> <dashed-function> Experimental <dashed-ident> <dimension> <display-box> <display-inside> <display-internal> <display-legacy> <display-listitem> <display-outside> <easing-function> <filter-function> <flex> <frequency-percentage> <frequency> <generic-family> <gradient> <hex-color> <hue-interpolation-method> <hue> <ident> <image> <integer> <length-percentage> <length> <line-style> <named-color> <number> <overflow-position> <overflow> <percentage> <position-area> <position> <ratio> <relative-size> <resolution> <self-position> <shape> Deprecated <string> <system-color> <text-edge> <time-percentage> <time> <timeline-range-name> <transform-function> <url> Functions -moz-image-rect Non-standard Deprecated abs() acos() anchor-size() anchor() asin() atan() atan2() attr() blur() brightness() calc-size() Experimental calc() circle() clamp() color-mix() color() conic-gradient() contrast-color() contrast() cos() counter() counters() cross-fade() cubic-bezier() device-cmyk() drop-shadow() dynamic-range-limit-mix() Experimental element() Experimental ellipse() env() exp() fit-content() grayscale() hsl() hue-rotate() hwb() hypot() if() Experimental image-set() image() inset() invert() lab() lch() light-dark() linear-gradient() linear() log() matrix() matrix3d() max() min() minmax() mod() oklab() oklch() opacity() paint() path() perspective() polygon() pow() progress() radial-gradient() ray() rect() rem() repeat() repeating-conic-gradient() repeating-linear-gradient() repeating-radial-gradient() rgb() rotate() rotate3d() rotateX() rotateY() rotateZ() round() saturate() scale() scale3d() scaleX() scaleY() scaleZ() sepia() shape() sibling-count() sibling-index() sign() sin() skew() skewX() skewY() sqrt() steps() superellipse() Experimental symbols() tan() translate() translate3d() translateX() translateY() translateZ() type() Experimental url() var() xywh() Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://4agc.com/donation_pages/9dda692c-6aa1-47e7-852d-58d396ebd3af | Project Implicit Edit View Calendar Search Info Next Previous Facebook Facebook Twitter Twitter Pinterest Instagram Youtube Linkedin Linkedin Link Email Actions /> Close Log In Keep the Science of Bias Accessible to All In This Moment, Understanding Matters More Than Ever We’re living in a time of deep division, rising misinformation, and pushback against equity and inclusion. We believe science and public access to research are essential, but that work is at risk . As a nonprofit organization, we rely on donor support to keep our educational site free and accessible. More than 25 million people have taken part in our research, helping to shape a more thoughtful and informed conversation about bias. If this work matters to you and you’re able to give, please consider donating today. Not in a position to give? You can make an impact by sharing the Project Implicit Website . Every donation and share helps us remain independent and keep our tools free and accessible to all. Read More Do not fill in this field Your Gift Monthly One-time $10 $25 $50 $100 $250 Round up my gift to $11 to help offset processing fees. Payment Information Debit or Credit Card Card Number Expiration Date Month 01 02 03 04 05 06 07 08 09 10 11 12 Year 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 CVV Security Code / CVV Number Visa, Mastercard, Discover Last 3 digits on back of card American Express 4 digits on front of card The Card Verification Value is the group of numbers immediately following your Visa, MasterCard, American Express and Discover credit card number. These numbers are used by your credit card company to help prevent fraud. This number is only used in processing your transaction and will not be recorded. Note: The digits are printed on your card, rather then stamped in the plastic like the digits in your credit card number. Donor Advised Fund Your Information First Name Last Name Email Yes, I would like to receive email updates. Country United States Canada Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Barbuda Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire Bosnia Botswana Bouvet Island Brazil British Indian Ocean Trty. Brunei Darussalam Bulgaria Burkina Faso Burundi Caicos Islands Cambodia Cameroon Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos (Keeling) Islands Colombia Comoros Congo Cook Islands Costa Rica Cote D'Ivoire Croatia Cuba Curaçao Cyprus Czech Republic Denmark Djibouti Dominica Dominican Republic East Timor Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands (Malvinas) Faroe Islands Fiji Finland France France, Metropolitan French Guiana French Polynesia French Southern Territories Futuna Islands Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guinea Guinea-Bissau Guyana Haiti Heard Herzegovina Honduras Hong Kong Hungary Iceland India Indonesia Iran (Islamic Republic of) Iraq Ireland Israel Italy Jamaica Jan Mayen Islands Japan Jordan Kazakhstan Kenya Kiribati Korea Korea (Democratic) Kuwait Kyrgystan Lao Latvia Lebanon Lesotho Liberia Libyan Arab Jamahiriya Liechtenstein Lithuania Luxembourg Macau Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mc Donald Islands Mexico Micronesia Miquelon Moldova Monaco Mongolia Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands Neutral Zone Nevis New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island Northern Mariana Islands Norway Oman Pakistan Palau Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Principe Puerto Rico Qatar Reunion Romania Russian Federation Rwanda Saba Saint Helena Saint Kitts Saint Lucia Saint Martin Saint Pierre Saint Vincent Samoa San Marino Sao Tome Saudi Arabia Senegal Seychelles Sierra Leone Singapore Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia South Sandwich Islands Spain St. Eustatius Sri Lanka Sudan Suriname Svalbard Swaziland Sweden Switzerland Syrian Arab Republic Taiwan Tajikistan Tanzania Thailand The Grenadines Tobago Togo Tokelau Tonga Trinidad Tunisia Turkey Turkmenistan Turks Islands Tuvalu Uganda Ukraine United Arab Emirates United Kingdom Uruguay US Minor Outlying Islands Uzbekistan Vanuatu Vatican City State Venezuela Viet Nam Virgin Islands (British) Virgin Islands (US) Wallis Western Sahara Yemen Yugoslavia Zaire Zimbabwe Address 1 Address 2 City State State Alabama (AL) Alaska (AK) Arizona (AZ) Arkansas (AR) Armed Forces Americas (AA) Armed Forces Europe (AE) Armed Forces Pacific (AP) California (CA) Colorado (CO) Connecticut (CT) Delaware (DE) District of Columbia (DC) Florida (FL) Georgia (GA) Guam (GU) Hawaii (HI) Idaho (ID) Illinois (IL) Indiana (IN) Iowa (IA) Kansas (KS) Kentucky (KY) Louisiana (LA) Maine (ME) Maryland (MD) Massachusetts (MA) Michigan (MI) Minnesota (MN) Mississippi (MS) Missouri (MO) Montana (MT) Nebraska (NE) Nevada (NV) New Hampshire (NH) New Jersey (NJ) New Mexico (NM) New York (NY) North Carolina (NC) North Dakota (ND) Ohio (OH) Oklahoma (OK) Oregon (OR) Pennsylvania (PA) Puerto Rico (PR) Rhode Island (RI) South Carolina (SC) South Dakota (SD) Tennessee (TN) Texas (TX) Utah (UT) Vermont (VT) Virginia (VA) Washington (WA) West Virginia (WV) Wisconsin (WI) Wyoming (WY) Zip Code Phone Remember my contact information on this browser. (Credit card information is not stored.) Amount $10 Donate Now By clicking the above button you agree to have your debit or credit card or bank account charged by Project Implicit. Your Donation is Secure Please wait... Project Implicit 6 Liberty Square #2344 Boston, MA 02109 US Privacy & Security Have questions or need help? 9178069076 admin@projectimplicit.net Powered by 4aGoodCause Terms & Conditions We Respect Your Privacy At our site, we do not collect personally identifiable information from individuals unless they provide it to us voluntarily and knowingly. This means we do not require you to register or provide information to us in order to view our site. We only gather personally identifiable data, such as names, addresses, zip/postal codes, email addresses, etc., when voluntarily submitted by a visitor. For example, personally identifiable information may be collected to receive our newsletter, or to make a financial contribution online. This information is used solely by us or other entities who are involved in the operation of this site for internal purposes. Use of your Personal Information We do not sell, rent or lease our donor lists to third parties. We may, from time to time, contact you about a special event related to our nonprofit that may be of interest to you. In those cases, your personal information (e-mail, name, address, telephone number) is not transferred to the third party outside of the nonprofit. We occasionally hire other companies to provide limited services on our behalf, such as handling the processing and delivery of mailings, providing customer support, processing transactions, or performing statistical analysis of our services. We will only provide those companies the personal information they need to deliver the service. In most cases, this is to deliver a direct mailing or emailing. They are required to maintain the confidentiality of your information and are prohibited from using that information for any other purpose. Your Credit Card Information Is Secure We care about the safety and security of your transaction. We employ a Server Digital Certificate and the Secure Sockets Layer (SSL) Protocol to encrypt all data traffic. They use high grade encryption and the https security protocol to communicate with your browser software. This method is the industry standard security protocol, and among the best software available today for secure commerce transactions. It encrypts all your personal information, so that it cannot be read over the internet. If you prefer, you may also make a donation over the phone. Refund Policy Please note: we do not sell any merchandise online, and as such there is no 'return policy.' Donations are considered non-refundable. | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/flutter-androidpush-integration | Android Push Setup (FCM) - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK SuprSend Client SDK Authentication Javascript Android iOS React Native Flutter Android Integration iOS Integration Manage Users Sync Events iOS Push Setup Android Push Setup (FCM) React Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Flutter Android Push Setup (FCM) Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Flutter Android Push Setup (FCM) OpenAI Open in ChatGPT Step-by-step guide to setup FCM Push notifications in flutter android app. OpenAI Open in ChatGPT Example integration project can be found here . Integration Steps 1 Create a Firebase project in the firebase console To start sending notifications from FCM, you’ll have to first create a firebase project. Create a firebase project and application in firebase console with your applications package name which you can find in AndroidManifest.xml 2 Adding google-services.json to your project You can get your Service Account JSON from Firebase Console Project Settings. Download google-services.json and add the file inside your android > app folder. 3 Adding Firebase dependencies and plugins 3.1. Add the below dependency inside projects build.gradle inside dependencies Groovy (build.gradle) Kotlin DSL (build.gradle.kts) Copy Ask AI dependencies { .. . classpath 'com.google.gms:google-services:4.3.10' // or latest version } 3.2. Add the below plugin inside the app build.gradle Groovy (build.gradle) Kotlin DSL (build.gradle.kts) Copy Ask AI apply plugin : 'com.google.gms.google-services' 3.3 Add the below dependency inside apps build.gradle inside dependencies Groovy (build.gradle) Kotlin DSL (build.gradle.kts) Copy Ask AI implementation( "com.google.firebase:firebase-messaging:22.0.0" ) // or latest version 4 Implementing push Push feature can be implemented in two ways: Token Generation and Notification handled By SDK [Recommended] You may use this option if all of your android push notifications are to be handled via SuprSend SDK. We recommend you use this method as it is just a single-step process to just register the service in your application manifest and everything else will be ready. AndroidManifest.xml Copy Ask AI <!--If you are targeting to API 33 (Android 13) you will additional need to add POST_NOTIFICATIONS --> < uses-permission android:name = "android.permission.POST_NOTIFICATIONS" /> < service android:name = "app.suprsend.fcm.SSFirebaseMessagingService" android:enabled = "true" android:exported = "false" > < intent-filter > < action android:name = "com.google.firebase.MESSAGING_EVENT" /> </ intent-filter > </ service > Token Generation and Notification handled By Your Application Once you get a token from Firebase you can pass the token by using the below code main.dart Copy Ask AI suprsend . setAndroidFcmPush ( fcm_token ); When you get a push notification you will get a payload and it can be passed to the method provided by Suprsend Flutter SDK and the notification displaying part will be handled by SDK. main.dart Copy Ask AI suprsend . showNotification ( notification_payload ); How to identify if notification is sent by SuprSend? If notification payload contains key supr_send_n_pl then simply consider this as payload sent from suprsend and pass the payload to suprsend sdk. Targeting Android 13 (API-33) In Android13 (API 33) or higher notification permission will be disabled by default so permission needs to be asked to enable notifications if you are targeting android 13 users. You can follow this doc to update to support Andriod 13(API 33), if not already supported. Please test the application as well as upgrading to API 33 may causes breaking changes. 1 Add POST_NOTIFICATIONS permission in AndroidManifest.xml if not present already. AndroidManifest.xml Copy Ask AI < manifest ... > < uses-permission android:name = "android.permission.POST_NOTIFICATIONS" /> < application ... > ... </ application > </ manifest > 2 Ask notification permission to show push notifications You can use permission_handler or any other package to ask notification permission to user. From v2.4.0, we have removed internal method to ask notification permission ( suprsend.askNotificationPermission ). You can use external package to ask notification permission. Once notification permission is granted, users can be able to see push notifications. Was this page helpful? Yes No Suggest edits Raise issue Previous SDK Integration SDK Integration to enable SuprSend features like Inbox, Preferences, and Webpush into React-based web applications. Next ⌘ I x github linkedin youtube Powered by On this page Integration Steps Targeting Android 13 (API-33) | 2026-01-13T08:48:25 |
https://dev.to/t/herokuchallenge | Heroku "Back to School" AI Challenge - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Heroku "Back to School" AI Challenge Follow Hide This is the official tag for submissions and announcements related to the Heroku "Back to School" AI Challenge. Create Post about #herokuchallenge Check out our latest challenge ! Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Stop Creating School Timetables Manually — Build Smart Scheduling Workflows with Academic Scheduler Muhammad Huzaifa Muhammad Huzaifa Muhammad Huzaifa Follow Oct 26 '25 Stop Creating School Timetables Manually — Build Smart Scheduling Workflows with Academic Scheduler # herokuchallenge # deved 2 reactions Comments Add Comment 1 min read Heroku "Back to School" AI Challenge: Winner Announcement Delayed Jess Lee Jess Lee Jess Lee Follow for The DEV Team Oct 9 '25 Heroku "Back to School" AI Challenge: Winner Announcement Delayed # herokuchallenge # devchallenge 2 reactions Comments 3 comments 1 min read Congrats to the Heroku "Back to School" AI Challenge Winners! dev.to staff dev.to staff dev.to staff Follow for The DEV Team Oct 13 '25 Congrats to the Heroku "Back to School" AI Challenge Winners! # devchallenge # herokuchallenge # heroku # ai 33 reactions Comments 9 comments 2 min read StudyFlow AI Julio Díaz Julio Díaz Julio Díaz Follow Sep 29 '25 StudyFlow AI # devchallenge # herokuchallenge # webdev # ai 26 reactions Comments 4 comments 2 min read AI-Powered Teacher Assistant: Revolutionizing Lesson Planning for Educators VICTOR LAKRA VICTOR LAKRA VICTOR LAKRA Follow Sep 28 '25 AI-Powered Teacher Assistant: Revolutionizing Lesson Planning for Educators # devchallenge # herokuchallenge # webdev # ai 15 reactions Comments 9 comments 3 min read BTS - Back to School Planner Assistant Nicanor Korir Nicanor Korir Nicanor Korir Follow Sep 28 '25 BTS - Back to School Planner Assistant # devchallenge # herokuchallenge # webdev # ai 8 reactions Comments Add Comment 2 min read TalkToMyTabs – A Back-to-School AI Reading & Research Assistant Jackson Kasi Jackson Kasi Jackson Kasi Follow Sep 28 '25 TalkToMyTabs – A Back-to-School AI Reading & Research Assistant # devchallenge # herokuchallenge # webdev # ai 12 reactions Comments Add Comment 5 min read Study-Mate: AI Powered Study Success Platform. Anshu Mandal Anshu Mandal Anshu Mandal Follow Sep 29 '25 Study-Mate: AI Powered Study Success Platform. # devchallenge # herokuchallenge # webdev # ai 37 reactions Comments 5 comments 9 min read Study Bud: AI-Powered Learning Companion AnurajBhaskar47 AnurajBhaskar47 AnurajBhaskar47 Follow Sep 29 '25 Study Bud: AI-Powered Learning Companion # devchallenge # herokuchallenge # webdev # ai 4 reactions Comments Add Comment 6 min read Study smart 🤓 ANIRUDDHA ADAK ANIRUDDHA ADAK ANIRUDDHA ADAK Follow Sep 28 '25 Study smart 🤓 # devchallenge # herokuchallenge # webdev # ai Comments Add Comment 2 min read Blazer AI: Intelligent Student Handbook and Website Assistant Zach Massey Zach Massey Zach Massey Follow Sep 27 '25 Blazer AI: Intelligent Student Handbook and Website Assistant # devchallenge # herokuchallenge # webdev # ai 6 reactions Comments 1 comment 4 min read 📚 AI Study Buddy – Your Smart Text Summarizer (Heroku Back to School AI Challenge) Bilal Aslam Bilal Aslam Bilal Aslam Follow Sep 27 '25 📚 AI Study Buddy – Your Smart Text Summarizer (Heroku Back to School AI Challenge) # challenge # herokuchallenge # python # flask 4 reactions Comments Add Comment 2 min read ClassMate AI: Your Smartest Study Buddy for the School Year Akash Kumar Akash Kumar Akash Kumar Follow Sep 26 '25 ClassMate AI: Your Smartest Study Buddy for the School Year # devchallenge # herokuchallenge # webdev # ai Comments Add Comment 1 min read AI-RateMyProfessors App Tomi Tomi Tomi Follow Sep 25 '25 AI-RateMyProfessors App # devchallenge # herokuchallenge # webdev # ai 7 reactions Comments Add Comment 3 min read AI-powered back-to-school assistant ANIRUDDHA ADAK ANIRUDDHA ADAK ANIRUDDHA ADAK Follow Sep 24 '25 AI-powered back-to-school assistant # devchallenge # herokuchallenge # webdev # ai 5 reactions Comments Add Comment 1 min read Reflects your project's purpose and functionality Joshua Solomon Joshua Solomon Joshua Solomon Follow Sep 18 '25 Reflects your project's purpose and functionality # devchallenge # herokuchallenge # webdev # ai 1 reaction Comments Add Comment 4 min read Two challenges and $6,000 in prizes! Get your submissions in by September 28. Jess Lee Jess Lee Jess Lee Follow for The DEV Team Sep 22 '25 Two challenges and $6,000 in prizes! Get your submissions in by September 28. # devchallenge # herokuchallenge # kendoreactchallenge # webdev 22 reactions Comments 1 comment 1 min read OmniLearn: Multi-Agent AI School Bots for Universal Childhood Education Maani K Maani K Maani K Follow Sep 14 '25 OmniLearn: Multi-Agent AI School Bots for Universal Childhood Education # devchallenge # herokuchallenge # webdev # ai Comments 3 comments 4 min read Student chat Rushikesh Pundkar Rushikesh Pundkar Rushikesh Pundkar Follow Aug 30 '25 Student chat # devchallenge # herokuchallenge # webdev # ai 15 reactions Comments 2 comments 1 min read Back to school Rushikesh Pundkar Rushikesh Pundkar Rushikesh Pundkar Follow Aug 29 '25 Back to school # devchallenge # herokuchallenge # webdev # ai 14 reactions Comments Add Comment 1 min read Study Buddy: AI-Powered Student Success Assistant Agastya Khati Agastya Khati Agastya Khati Follow Aug 28 '25 Study Buddy: AI-Powered Student Success Assistant # devchallenge # herokuchallenge # webdev # ai 14 reactions Comments Add Comment 2 min read Yeah, totally not a "Back-To-School" Challenge Dev.To AspXone AspXone AspXone Follow Aug 29 '25 Yeah, totally not a "Back-To-School" Challenge Dev.To # jokes # herokuchallenge 3 reactions Comments 7 comments 1 min read Back to school list Rushikesh Pundkar Rushikesh Pundkar Rushikesh Pundkar Follow Aug 29 '25 Back to school list # devchallenge # herokuchallenge # webdev # ai 9 reactions Comments 2 comments 1 min read Join the Heroku "Back to School" AI Challenge: $3,000 in Prizes, just for students! dev.to staff dev.to staff dev.to staff Follow for The DEV Team Aug 27 '25 Join the Heroku "Back to School" AI Challenge: $3,000 in Prizes, just for students! # herokuchallenge # devchallenge # ai # machinelearning 101 reactions Comments 36 comments 5 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/sms-template#sms-fields-description | SMS Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors SMS Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors SMS Template OpenAI Open in ChatGPT How to design and publish SMS template. OpenAI Open in ChatGPT Design Template You can design SMS template on SuprSend with a simple form editor tool. You can add variables with Handlebarsjs language. You can check how the message will look in the preview section on the right side. The SMS template has 3 parts: Message type (Transactional, Promotional, Engagement), Header (template headers added in the SMS integration settings), Body (SMS template is added here). Once designed, you can save the SMS template by clicking on “Save” button. When you are ready, you can Publish Draft by providing a name to the version. This will create a version in ‘Pending Approval’ state. Every SMS template goes through an approval process, where the templates are submitted to the registered DLT portal for review, where the SMS is reviewed based on the DLT guidelines and SMS either gets approved or rejected. SuprSend handles the template approval process for you. All you have to do is create a template on SuprSend while following DLT template guidelines, and wait for the approval / rejection of template. Accordingly, the published template version’s state will move to Live or Rejected . Once the version goes Live , you can use the template to send to your users. SMS fields description Field Description Message Type There are 3 types of message - (1) Transactional - Service implicit or Informative messages which are triggered corresponding to a user’s action either done at the time of sending the message or based on past data. All other OTPs other than bank OTPs also fall in this category. e.g.- delivery updates, E-commerce website OTPs etc. (2) Promotional - All the marketing related messages where we have not taken any explicit consent from the user. e.g.- messages sent to promote or sell a product (3) Engagement - Service Explicit or Engagement messages which are triggered to re-engage the users back to platform like promoting new features and offers. e.g.- new feature promotion, discount offer messages to existing customers etc. Header Header should be registered with DLT. Separate headers would be there for all the message types Body SMS template added here should follow DLT template guidelines. Click here to view all DLT guidelines Please note that to send the SMS, you will need to integrate SMS vendor with SuprSend. Please visit the ‘Vendor Integration Guideline’ section to see vendors list and how to integrate them. Vendor Integration Required 📘 Please note that to send the SMS, you will need to integrate SMS vendor with SuprSend. Please visit the ‘Vendor Integration Guideline’ section to see vendors list and how to integrate them. Adding dynamic content in SMS There will always be the case where you would be required to add dynamic content to a template, so as to personalise it for your users. To achieve this, you can add variables in the template, which will be replaced with the dynamic content at the time of sending email. To send actual values to replace variables at the time of communication trigger, use one of our frontend or backend SDKs. Here is a step by step guide on how to add dynamic content in a template: 1 Declaring Variables in the global 'Mock data' button: If you are at this stage, it is assumed that you have declared the variables along with sample values in the global Mock data button. To see how to declare variables before using them in designing templates, refer to this section in the Templates documentation . 2 Using variables in the templates: Once the variables are declared, you can use them while designing template for any channel. We support handlebarsjs to add variables in the template. As a general rule, all the variables have to be entered within double curly brackets: {{variable\_name}} If you have declared the variables and added sample data in the global Mock data button, then they will come as auto-suggestions when you type a curly bracket { . This will remove the chances of error like variable mismatch at the time of template rendering. Note that you will be able to enter a variable name even when you have not declared it inside the Variables button. To manually enter the variable name, follow the handlerbarsjs guide here . Below are some examples of how to enter variables in the template design. For illustration, we are using the same sample variable names that we declared in the Templates section: json Copy Ask AI { "array" : [ { "product_name" : "Aldo Sling Bag" , "product_price" : "3,950.00" }, { "product_name" : "Clarles & Keith Women Slipper, Biege, 38UK" , "product_price" : "2,549.00" }, { "product_name" : "RayBan Sunglasses" , "product_price" : "7,899.00" } ], "event" : { "location" : { "city" : "Bangalore" , "state" : "KA" }, "order_id" : "11200123" , "first_name" : "Nikita" }, "product_page" : "https://www.suprsend.com" } To enter a nested variable, enter in the format {{var1.var2.var3}} . Eg. to refer to city in the example above, you need to enter {{event.location.city}} If you have any space in the variable name, enclose it in square bracket {{event.[first name]}} To refer to an array element, enter in format {{var1.[index].var2}} . Eg. to refer to product_name of the first element of the array array , enter {{array.[0].product_name}} At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user. Please note that the rest of the templates will be sent. Eg. if there is an error in rendering Android Push template, but SMS template is successfully rendered, Android Push notification will not be triggered, but SMS notification will be triggered by SuprSend. Was this page helpful? Yes No Suggest edits Raise issue Previous Whatsapp Template How to design whatsapp template using form editor. Next ⌘ I x github linkedin youtube Powered by On this page Design Template SMS fields description Adding dynamic content in SMS | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API | Service Worker API - Web APIs | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Web APIs Service Worker API Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) Service Worker API Note: This feature is available in Web Workers . Service workers essentially act as proxy servers that sit between web applications, the browser, and the network (when available). They are intended, among other things, to enable the creation of effective offline experiences, intercept network requests, and take appropriate action based on whether the network is available, and update assets residing on the server. They will also allow access to push notifications and background sync APIs. Note: Service workers are a type of web worker. See Web workers for general information about worker types and use cases. In this article Service worker concepts and usage Other use case ideas Interfaces Specifications See also Service worker concepts and usage A service worker is an event-driven worker registered against an origin and a path. It takes the form of a JavaScript file that can control the web page/site that it is associated with, intercepting and modifying navigation and resource requests, and caching resources in a very granular fashion to give you complete control over how your app behaves in certain situations (the most obvious one being when the network is not available). Service workers run in a worker context: they therefore have no DOM access and run on a different thread to the main JavaScript that powers your app. They are non-blocking and designed to be fully asynchronous. As a consequence, APIs such as synchronous XHR and Web Storage can't be used inside a service worker. Service workers can't import JavaScript modules dynamically, and import() will throw an error if it is called in a service worker global scope. Static imports using the import statement are allowed. Service workers are only available in secure contexts : this means that their document is served over HTTPS, although browsers also treat http://localhost as a secure context, to facilitate local development. HTTP connections are susceptible to malicious code injection by man in the middle attacks, and such attacks could be worse if allowed access to these powerful APIs. Note: On Firefox, for testing you can run service workers over HTTP (insecurely); simply check the Enable Service Workers over HTTP (when toolbox is open) option in the Firefox DevTools options/gear menu. Note: Unlike previous attempts in this area such as AppCache , service workers don't make assumptions about what you are trying to do, but then break when those assumptions are not exactly right. Instead, service workers give you much more granular control. Note: Service workers make heavy use of promises , as generally they will wait for responses to come through, after which they will respond with a success or failure action. The promises architecture is ideal for this. Registration A service worker is first registered using the ServiceWorkerContainer.register() method. If successful, your service worker will be downloaded to the client and attempt installation/activation (see below) for URLs accessed by the user inside the whole origin, or a subset specified by you. Download, install and activate At this point, your service worker will observe the following lifecycle: Download Install Activate The service worker is immediately downloaded when a user first accesses a service worker–controlled site/page. After that, it is updated when: A navigation to an in-scope page occurs. An event is fired on the service worker and it hasn't been downloaded in the last 24 hours. Installation is attempted when the downloaded file is found to be new — either different to an existing service worker (byte-wise compared), or the first service worker encountered for this page/site. If this is the first time a service worker has been made available, installation is attempted, then after a successful installation, it is activated. If there is an existing service worker available, the new version is installed in the background, but not yet activated — at this point it is called the worker in waiting . It is only activated when there are no longer any pages loaded that are still using the old service worker. As soon as there are no more pages to be loaded, the new service worker activates (becoming the active worker ). Activation can happen sooner using ServiceWorkerGlobalScope.skipWaiting() and existing pages can be claimed by the active worker using Clients.claim() . You can listen for the install event; a standard action is to prepare your service worker for usage when this fires, for example by creating a cache using the built-in storage API, and placing assets inside it that you'll want for running your app offline. There is also an activate event. The point where this event fires is generally a good time to clean up old caches and other things associated with the previous version of your service worker. Your service worker can respond to requests using the FetchEvent event. You can modify the response to these requests in any way you want, using the FetchEvent.respondWith() method. Note: Because install / activate events could take a while to complete, the service worker spec provides a waitUntil() method. Once it is called on install or activate events with a promise, functional events such as fetch and push will wait until the promise is successfully resolved. For a complete tutorial to show how to build up your first basic example, read Using Service Workers . Using static routing to control how resources are fetched Service workers can incur an unnecessary performance cost — when a page is loaded for the first time in a while, the browser has to wait for the service worker to start up and run to know what content to load and whether it should come from a cache or the network. If you already know ahead of time where certain content should be fetched from, you can bypass the service worker altogether and fetch resources immediately. The InstallEvent.addRoutes() method can be used to implement this use case and more. Other use case ideas Service workers are also intended to be used for such things as: Background data synchronization. Responding to resource requests from other origins. Receiving centralized updates to expensive-to-calculate data such as geolocation or gyroscope, so multiple pages can make use of one set of data. Client-side compiling and dependency management of CoffeeScript, less, CJS/AMD modules, etc. for development purposes. Hooks for background services. Custom templating based on certain URL patterns. Performance enhancements, for example, pre-fetching resources that the user is likely to need soon, such as the next few pictures in a photo album. API mocking. In the future, service workers will be able to do several other useful things for the web platform that will bring it closer to native app viability. Interestingly, other specifications can and will start to make use of the service worker context, for example: Background synchronization : Start up a service worker even when no users are at the site, so caches can be updated, etc. Reacting to push messages : Start up a service worker to send users a message to tell them new content is available. Reacting to a particular time & date. Entering a geo-fence. Interfaces Cache Represents the storage for Request / Response object pairs that are cached as part of the ServiceWorker life cycle. CacheStorage Represents the storage for Cache objects. It provides a master directory of all the named caches that a ServiceWorker can access, and maintains a mapping of string names to corresponding Cache objects. Client Represents the scope of a service worker client. A service worker client is either a document in a browser context or a SharedWorker , which is controlled by an active worker. Clients Represents a container for a list of Client objects; the main way to access the active service worker clients at the current origin. ExtendableEvent Extends the lifetime of the install and activate events dispatched on the ServiceWorkerGlobalScope , as part of the service worker lifecycle. This ensures that any functional events (like FetchEvent ) are not dispatched to the ServiceWorker , until it upgrades database schemas, and deletes outdated cache entries, etc. ExtendableMessageEvent The event object of a message event fired on a service worker (when a channel message is received on the ServiceWorkerGlobalScope from another context) — extends the lifetime of such events. FetchEvent The parameter passed into the onfetch handler, FetchEvent represents a fetch action that is dispatched on the ServiceWorkerGlobalScope of a ServiceWorker . It contains information about the request and resulting response, and provides the FetchEvent.respondWith() method, which allows us to provide an arbitrary response back to the controlled page. InstallEvent The parameter passed into an install event handler function, the InstallEvent interface represents an install action that is dispatched on the ServiceWorkerGlobalScope of a ServiceWorker . As a child of ExtendableEvent , it ensures that functional events such as FetchEvent are not dispatched during installation. NavigationPreloadManager Provides methods for managing the preloading of resources with a service worker. ServiceWorker Represents a service worker. Multiple browsing contexts (e.g., pages, workers, etc.) can be associated with the same ServiceWorker object. ServiceWorkerContainer Provides an object representing the service worker as an overall unit in the network ecosystem, including facilities to register, unregister, and update service workers, and access the state of service workers and their registrations. ServiceWorkerGlobalScope Represents the global execution context of a service worker. ServiceWorkerRegistration Represents a service worker registration. WindowClient Represents the scope of a service worker client that is a document in a browser context, controlled by an active worker. This is a special type of Client object, with some additional methods and properties available. Extensions to other interfaces Window.caches and WorkerGlobalScope.caches Returns the CacheStorage object associated with the current context. Navigator.serviceWorker and WorkerNavigator.serviceWorker Returns a ServiceWorkerContainer object, which provides access to registration, removal, upgrade, and communication with the ServiceWorker objects for the associated document . Specifications Specification Service Workers Nightly See also Using Service Workers Service Worker Lifecycle Service workers basic code example Web APIs that are related to the Service Worker API: Background Fetch API Background Synchronization API Content Index API Cookie Store API Notifications API Payment Handler API Push API Web Periodic Background Synchronization API Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 30, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Service Worker API Guides Using Service Workers Interfaces Cache CacheStorage Client Clients ExtendableEvent ExtendableMessageEvent FetchEvent InstallEvent NavigationPreloadManager ServiceWorker ServiceWorkerContainer ServiceWorkerGlobalScope ServiceWorkerRegistration WindowClient Properties Window .caches WorkerGlobalScope .caches Navigator .serviceWorker WorkerNavigator .serviceWorker Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/tenant-preference | Tenant Preferences - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences User Preferences Tenant Preferences Preference Evaluation Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Preferences Tenant Preferences Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Preferences Tenant Preferences OpenAI Open in ChatGPT Learn how to manage preferences for your tenants and their users. OpenAI Open in ChatGPT Tenants (previously named as brands) represent a segment that users belong to. They can be organizations, teams within an organization, subsidiary companies, or different product lines in the same business. If you’re a B2B application or a multi-tenant SaaS product, you can use tenant preferences to allow platform admins to control what tenants can access, or allow tenant admins to set default preferences for their users. How tenant preferences work Tenant preferences sit between global category defaults and user preferences. They let platform admins restrict what a tenant can access, and let tenant admins override defaults for their users. Notifications are sent only if the category and channel are allowed at all three levels. Platform admin: Controlling tenant access As a platform administrator, you can define which notification categories and channels are available to different tenants. For example, if you’re a SaaS platform with paid features and some clients haven’t subscribed to those features, you can hide notification categories related to the paid features for those tenants. 1 Access tenant settings Go to the tenant details page on SuprSend dashboard 2 Disable categories or channels Disable categories or set channels as opt-out that aren’t valid for specific tenants 3 Save changes Tenants won’t be able to set preferences in hidden categories, and notifications won’t be sent to tenant users in those categories Tenant preference controls in the SuprSend dashboard Tenant admin: Setting defaults for their users Tenant administrators can set default preferences for their end users and hide categories that aren’t applicable to their users. This gives tenant admins control over which notifications are sent to their users and which categories appear on their users’ preference pages. Tenant admins can override category defaults and hide categories that don’t apply to their users. These overrides apply only to that tenant and don’t change global category defaults. Common scenarios: Hide entire sections (e.g., Sales section) from users’ preference pages Override channel requirements (e.g., make email mandatory for System categories) Hide specific categories while keeping others visible You can set tenant defaults via API or through SuprSend dashboard. Via API Use the tenant preference API to programmatically manage preferences Via Dashboard Configure from the tenant details page → Tenant Preference tab Controlling preference UI for users Tenants can control which categories appear on their users’ preference pages and which notifications are sent. Platform Admin Actions Tenant Admin Actions Impact & Precedence Turning off categories or channels for a tenant from the tenant preference page automatically removes them from the user’s preference view. Hidden categories won’t send notifications to tenant users, even if they previously opted in. Tenants can’t set preferences in categories disabled by the platform admin. Set visible_to_subscriber: false in default tenant preferences to hide categories from tenant users’ preference pages. This allows tenant admins to further limit visibility beyond platform-level settings. Hidden categories are removed from user preference APIs and UI view for that tenant’s users. Categories hidden via visible_to_subscriber: false won’t appear on preference pages Tenant-level category overrides take precedence over user preferences Channel preferences: If a platform admin disables a channel for a tenant, it cannot be re-enabled by the tenant or user Collecting preferences from tenant users You can load user preferences for a tenant by passing tenant_id in REST APIs and preference centre SDK . The hosted preference page automatically loads preferences corresponding to the tenant passed in the workflow trigger. Example API call: Copy Ask AI GET /v1/user/{distinct_id}/preference/?tenant_id=acme-inc REST APIs Use preference APIs with tenant_id parameter Preference Center SDK Embed preference center in your app For implementation details, see Capturing User Preferences . Triggering tenant workflows You can trigger tenant workflows by passing tenant_id in your workflow trigger. Passing tenant_id ensures the workflow resolves $tenant.* variables (branding, preferences, routing) before sending notifications. This enables tenant-level customizations including template design, notification preferences, and vendor routing. Read more about tenant workflows here . How tenant preferences are evaluated When a workflow is triggered, preferences are evaluated for both the recipient and tenant before each delivery node. Notifications are sent only in categories and channels where both tenant and user preferences are opt_in . The evaluation follows the precedence order: User Preference → Tenant Default → Category Default . Platform admin restrictions override all—if a platform admin disables a category or channel for a tenant, users will not receive notifications in that category, even if they previously opted in. For detailed information on how preferences are evaluated at runtime, including debugging steps, see Preference Evaluation . Was this page helpful? Yes No Suggest edits Raise issue Previous Preference Evaluation How SuprSend evaluates user preferences when sending notifications. Next ⌘ I x github linkedin youtube Powered by On this page How tenant preferences work Platform admin: Controlling tenant access Tenant admin: Setting defaults for their users Controlling preference UI for users Collecting preferences from tenant users Triggering tenant workflows How tenant preferences are evaluated | 2026-01-13T08:48:25 |
https://docs.suprsend.com/reference/mcp-quickstart | MCP Quickstart - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation MCP MCP Quickstart Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog MCP MCP Quickstart OpenAI Open in ChatGPT Get up and running with SuprSend MCP Server in minutes. Complete setup, authentication, and start using right away. OpenAI Open in ChatGPT Follow the steps below to set up the SuprSend MCP Server and start integrating SuprSend using your favourite AI assistant. Step 1: Install SuprSend CLI The MCP Server is powered through the SuprSend CLI for server startup and authentication. Install the CLI using the method that best fits your OS and usecase. Homebrew (Recommended) Binary Releases Source Build For macOS or Linux users Copy Ask AI brew tap suprsend/tap brew install --cask suprsend Best for Windows users, servers or CI/CD environments Download the binary from GitHub Releases and then install it using: Copy Ask AI # Linux/macOS chmod +x suprsend sudo mv suprsend /usr/local/bin/ # Windows: Extract suprsend.exe to your PATH Best for project contributors or advanced users who want to always have access to the latest binary. Requires Go (version 1.20 or later) Copy Ask AI # 1. Clone the repository git clone https://github.com/suprsend/cli.git cd cli/cmd/suprsend # 2. Build the binary go build -o suprsend # 3. Move the binary to your PATH for easy access sudo mv suprsend /usr/local/bin/ Step 2: Get Your Service Token You’ll need a service token from SuprSend to authenticate MCP Server. Get your service token from SuprSend Dashboard → Account Settings → Service Tokens . Step 3: Authenticate CLI Best way to authenticate CLI for local development is to set up environment variable . You can either set it in your shell Copy Ask AI export SUPRSEND_SERVICE_TOKEN = "your_service_token_here" Or pass the environment variable directly in your MCP configuration. Copy Ask AI { "mcpServers" : { "suprsend" : { "command" : "suprsend" , "args" : [ "start-mcp-server" ], "env" : { "SUPRSEND_SERVICE_TOKEN" : "your_service_token_here" } } } } Step 4: Set Up MCP in your AI coding assistants Cursor Click on this button to install the SuprSend MCP server in Cursor (version 1.0 or higher is required). Or, add the MCP configuration manually to your Cursor settings. Go to Cursor -> Settings -> Cursor Settings On the settings modal, Go to MCP & Integrations and click on “New MCP Server”. Inside mcp.json file, add below code: Copy Ask AI { "mcpServers" : { "suprsend" : { "command" : "suprsend" , "args" : [ "start-mcp-server" ], "env" : { "SUPRSEND_SERVICE_TOKEN" : "your_service_token_here" } } } } Claude Desktop Open Claude Settings → Developer Section. Click Edit Config under Local MCP Servers. Add the following snippet: Copy Ask AI { "mcpServers" : { "suprsend" : { "command" : "suprsend" , "args" : [ "start-mcp-server" ], "env" : { "SUPRSEND_SERVICE_TOKEN" : "your_service_token_here" } } } } Windsurf Go to Windsurf settings → Extensions Add the SuprSend MCP configuration Copy Ask AI { "suprsend" : { "command" : "suprsend" , "args" : [ "start-mcp-server" ], "env" : { "SUPRSEND_SERVICE_TOKEN" : "your_service_token_here" }, "name" : "SuprSend MCP Server" } } Refresh the MCP Settings by clicking the refresh button. Was this page helpful? Yes No Suggest edits Raise issue Previous Tool List Complete reference of all available tools in the SuprSend MCP server Next ⌘ I x github linkedin youtube Powered by On this page Step 1: Install SuprSend CLI Step 2: Get Your Service Token Step 3: Authenticate CLI Step 4: Set Up MCP in your AI coding assistants Cursor Claude Desktop Windsurf | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API | Fetch API - Web APIs | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Web APIs Fetch API Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Fetch API The Fetch API provides an interface for fetching resources (including across the network). It is a more powerful and flexible replacement for XMLHttpRequest . In this article Concepts and usage Interfaces HTTP headers Specifications Browser compatibility See also Concepts and usage The Fetch API uses Request and Response objects (and other things involved with network requests), as well as related concepts such as CORS and the HTTP Origin header semantics. For making a request and fetching a resource, use the fetch() method. It is a global method in both Window and Worker contexts. This makes it available in pretty much any context you might want to fetch resources in. The fetch() method takes one mandatory argument, the path to the resource you want to fetch. It returns a Promise that resolves to the Response to that request — as soon as the server responds with headers — even if the server response is an HTTP error status . You can also optionally pass in an init options object as the second argument (see Request ). Once a Response is retrieved, there are a number of methods available to define what the body content is and how it should be handled. You can create a request and response directly using the Request() and Response() constructors, but it's uncommon to do this directly. Instead, these are more likely to be created as results of other API actions (for example, FetchEvent.respondWith() from service workers). Find out more about using the Fetch API features in Using Fetch . Deferred Fetch The fetchLater() API enables a developer to request a deferred fetch , that can be sent after a specified period of time, or when the page is closed or navigated away from. See Using Deferred Fetch . Interfaces Window.fetch() and WorkerGlobalScope.fetch() The fetch() method used to fetch a resource. Window.fetchLater() Used to make a deferred fetch request. DeferredRequestInit Represents the set of options that can be used to configure a deferred fetch request. FetchLaterResult Represents the result of requesting a deferred fetch. Headers Represents response/request headers, allowing you to query them and take different actions depending on the results. Request Represents a resource request. Response Represents the response to a request. HTTP headers deferred-fetch Controls the top-level quota for the fetchLater() API. deferred-fetch-minimal Controls the shared cross-origin subframe quota for the fetchLater() API. Specifications Specification Fetch # fetch-method Fetch # deferred-fetch Browser compatibility api.fetch Enable JavaScript to view this browser compatibility table. api.Window.fetchLater Enable JavaScript to view this browser compatibility table. See also Using Fetch Service Worker API HTTP access control (CORS) HTTP Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jan 8, 2026 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Fetch API Guides Using the Fetch API Using Deferred Fetch Interfaces DeferredRequestInit Experimental FetchLaterResult Experimental Headers Request RequestInit Response Methods Window .fetch() WorkerGlobalScope .fetch() Window .fetchLater() Experimental Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/CSS_layout | CSS layout - Learn web development | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Learn Core learning modules CSS layout Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) CSS layout Overview: Core learning modules Next In previous modules we looked at how to style and manipulate the boxes that your content sits inside. Now it's time to look at how to correctly lay out your boxes in relation to one another, and the browser viewport. This module looks at floats, positioning, other modern layout tools, and building responsive designs that will adapt to different devices, screen sizes, and resolutions. In this article Prerequisites Tutorials and challenges Test your skills Additional tutorials See also Prerequisites Before starting this module, you should be familiar with HTML , the basic fundamentals of CSS , and CSS text styling . Note: If you are working on a computer, tablet, or another device where you can't create files, you can try running the code in an online editor such as CodePen or JSFiddle . Tutorials and challenges Introduction to CSS layout This lesson recaps some of the CSS layout features we've already touched upon in previous modules, such as different display values, as well as introducing some of the concepts we'll be covering throughout this module. It also covers the concept of normal flow in depth. Floats Originally for floating images inside blocks of text, the float property became one of the most commonly used tools for creating multiple column layouts on webpages. With the advent of flexbox and grid it has now returned to its original purpose, as this article explains. Positioning Positioning allows you to take elements out of normal document flow and make them behave differently, for example, sitting on top of one another or always remaining in the same place inside the browser viewport. This article explains the different position values and how to use them. Flexbox Flexbox is a one-dimensional layout method for laying out items in rows or columns. Items flex to fill additional space and shrink to fit into smaller spaces. This article explains all the fundamentals. CSS grid layout CSS grid layout is a two-dimensional layout system for the web. It lets you organize content into rows and columns and offers many features to simplify the creation of complex layouts. This article will explain all you need to know to get started with grid layout. Fundamental layout comprehension Challenge This challenge will test your knowledge of the layout features we've covered so far in the module, namely flexbox, floats, grid, and positioning. By the end you will have developed a webpage layout using a variety of techniques. Responsive design As more diverse screen sizes have appeared on web-enabled devices, the concept of responsive web design (RWD) has appeared: a set of practices that allows web pages to alter their layout and appearance to suit different screen widths, resolutions, etc. It is an idea that changed the way we design for a multi-device web, and in this article we'll help you understand the main techniques you need to know to master it. Media query fundamentals The CSS Media Query gives you a way to apply CSS only when the browser and device environment matches rules that you specify. Media queries are a key part of responsive web design because they allow you to create different layouts depending on the size of the viewport. In this lesson, you will learn about the syntax used in media queries then use them in an interactive example showing how a simple design might be made responsive. Test your skills You will find "Test your skills" articles placed between the tutorial articles to check whether you have retained the most important information before you move on. If you want to explore all of these together, you can find them listed at Test your skills: CSS layout . Additional tutorials These tutorials are not part of the learning pathway, but they are interesting nonetheless — you should consider these as stretch goals, to optionally study when you are done with the main Core articles. Multiple-column layout The multiple-column layout specification provides you with a method for laying content out in columns, as you might see in a newspaper. This article explains how to use this feature. Practical positioning examples This article shows how to build some real-world examples to illustrate what kinds of things you can do with positioning. Legacy layout methods Grid systems are a very common feature used in CSS layouts, and before CSS grid layout they tended to be implemented using floats or other layout features. You imagine your layout as a set number of columns (e.g., 4, 6, or 12), and then fit your content columns inside these imaginary columns. In this article we'll explore how these older methods work, in order that you understand how they were used if you work on an older project. Supporting older browsers Visitors to your website may include users who either use older browsers or use browsers that do not support the CSS features you've implemented. This is a common scenario on the web, where new features are continuously being added to CSS. Browsers differ in their support for these features because different browsers tend to prioritize implementing different features. This article explains how you as a web developer can use modern web techniques to ensure that your website remains accessible to users with older technology. See also CSS layout cookbook The CSS layout cookbook aims to bring together recipes for common layout patterns, things you might need to implement in your sites. In addition to providing code you can use as a starting point in your projects, these recipes highlight the different ways layout specifications can be used and the choices you can make as a developer. Learn Flexbox and Learn CSS Grid MDN learning partner These courses from Scrimba provide interactive lessons teaching you all you need to know about Flexbox and Grid. Overview: Core learning modules Next Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 7, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Learn web development MDN curriculum Getting started modules Environment setup Installing software Browsing the web Code editors Dealing with files Command line Your first website What will it look like? Creating the content Styling the content Adding interactivity Publishing Web standards How the web works The web standards model How browsers load websites Soft skills Research and learning Collaboration and teamwork Workflows and processes Finding a job Core modules Structuring content with HTML Basic HTML syntax Web page metadata Headings and paragraphs Emphasis and importance Lists Test: HTML text basics Advanced text features Test: Advanced HTML text Challenge: Letter markup Structuring documents Creating links Test: Links Challenge: Bird watching site Images Test: Images Video and audio Test: Audio and video Challenge: Splash page Table basics Table accessibility Challenge: Planet data table Forms and buttons Test: Forms and buttons Challenge: Feedback form Debugging HTML Test: HTML tests index Additional tutorials Vector graphics Embedding technologies CSS styling basics What is CSS? CSS getting started Challenge: Biography page Basic selectors Attribute selectors Pseudo-classes and elements Combinators Test: Selectors Box model Test: Box model Handling conflicts Test: Cascade Challenge: Fixing blog styles Values and units Test: Values and units Sizing Test: Sizing Backgrounds and borders Test: Backgrounds and borders Overflow Test: Overflow Challenge: Sizing and decorating Images, media, forms Test: Images and forms Styling tables Challenge: Styling color scheme search Debugging CSS Test: Styling basics tests index Additional tutorials Advanced styling effects Cascade layers Multiple text directions Organizing your CSS CSS text styling Text and font fundamentals Styling lists Styling links Web fonts Challenge: Community school homepage CSS layout Introduction Floats Test: Floats Positioning Test: Positioning Flexbox Test: Flexbox CSS grid layout Test: CSS grid Challenge: Fundamental layout Responsive web design Media queries Test: RWD & media queries Challenge: mobile-first Test: Layout tests index Additional tutorials Multiple-column layout Practical positioning examples Legacy layout methods Supporting older browsers Dynamic scripting with JavaScript What is JavaScript? JavaScript walkthrough Troubleshooting Variables Test: Variables Numbers and operators Test: Math Strings String methods Test: Strings Arrays Test: Arrays Challenge: Story generator Conditionals Test: Conditionals Loops Test: Loops Functions Build your own function Function return values Test: Functions Events Event bubbling Test: Events Objects Test: Objects DOM scripting Challenge: Image gallery Network requests JSON Test: JSON Challenge: House data UI Debugging and error handling Test: JavaScript tests index JavaScript frameworks and libraries Introduction Framework features React getting started React ToDo app React components React events and state React editing, filtering, conditional UI React accessibility React resources Accessibility What is accessibility? Accessibility tools Accessible HTML Test: HTML a11y Accessible CSS and JS Test: CSS/JS a11y WAI-ARIA Test: WAI-ARIA Accessible multimedia Mobile accessibility Challenge: A11y debugging Test: A11y tests index Design for developers Version control Extension modules Advanced JavaScript objects Object prototypes Object-oriented programming Classes in JavaScript Test: Object-oriented JavaScript Object building practice Challenge: Bouncing balls features Test: OOJS tests index Client-side web APIs Introduction Video and audio Drawing graphics Client-side storage Third-party APIs Asynchronous JavaScript Introduction Using promises Implementing promise-based APIs Introducing workers Challenge: Animation sequence Web forms Your first form How to structure a web form Basic native form controls The HTML5 input types Other form controls Styling web forms Advanced form styling Customizable selects UI pseudo-classes Client-side form validation Sending form data Additional tutorials Custom form controls JS form submission Forms in legacy browsers UI methods & controls Understanding client-side tools Overview Package management Sample toolchain Deploying our app Server-side websites First steps Introduction Client-server overview Server-side frameworks Website security Django (Python) Django introduction Dev environment setup 1: Local library tutorial 2: Skeleton website 3: Models 4: Django admin site 5: Home page 6: Generic list and detail views 7: Sessions framework 8: Authentication and permissions 9: Forms 10: Testing 11: Deploying Django security Challenge: Django blog Express (Node.js) Express/Node introduction Dev environment setup 1: Local library tutorial 2: Skeleton website 3: Using databases with Mongoose 4: Routes and controllers 5: Displaying data 6: Working with forms 7: Deploying Additional tutorials Apache .htaccess Server MIME type config Plain Node.js server Web performance The "why" of web performance What is web performance? Perceived performance Measuring performance Multimedia: Images Multimedia: video Performant JavaScript Performant HTML Performant CSS Performance business case Best practices & tips Testing Introduction Testing strategies Common HTML and CSS problems Feature detection Automated testing Automation environment setup Further resources How to solve common problems Common CSS problems Common HTML problems Common JavaScript problems Design and accessibility Tools and setup Web mechanics About Resources for educators Changelog Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:25 |
https://dev.to/t/webdev/page/77 | Web Development Page 77 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Web Development Follow Hide Because the internet... Create Post submission guidelines Be nice. Be respectful. Assume best intentions. Be kind, rewind. Older #webdev posts 74 75 76 77 78 79 80 81 82 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu I Built a Free Theme Generator for Developers — MVP Launch StyloFront StyloFront StyloFront Follow Dec 18 '25 I Built a Free Theme Generator for Developers — MVP Launch # frontend # css # ui # webdev 1 reaction Comments 1 comment 1 min read I Built a Free Tools Site for Developers — MVP Launch & Looking for Feedback StyloFront StyloFront StyloFront Follow Dec 18 '25 I Built a Free Tools Site for Developers — MVP Launch & Looking for Feedback # buildinpublic # webdev # frontend # tooling 1 reaction Comments 1 comment 1 min read Dompurify : Prevent XSS Attack remove all the script tag. Anupam Pandey Anupam Pandey Anupam Pandey Follow Dec 17 '25 Dompurify : Prevent XSS Attack remove all the script tag. # webdev # javascript # dompurify # programming Comments Add Comment 1 min read How to Choose the Right Tech Stack for Your Software Project Priya dharshini Priya dharshini Priya dharshini Follow Dec 17 '25 How to Choose the Right Tech Stack for Your Software Project # webdev # programming # ai # opensource Comments Add Comment 3 min read Our SEO Journey: From SPA to Next.js (The Complete Playbook) Bishoy Semsem Bishoy Semsem Bishoy Semsem Follow Dec 16 '25 Our SEO Journey: From SPA to Next.js (The Complete Playbook) # react # webdev Comments Add Comment 5 min read TailAdmin Laravel: Laravel Admin Dashboard Built with Tailwind and Blade TailAdmin TailAdmin TailAdmin Follow Dec 18 '25 TailAdmin Laravel: Laravel Admin Dashboard Built with Tailwind and Blade # laravel # opensource # webdev # productivity 46 reactions Comments 1 comment 4 min read I Asked AI to Invent 54 Cocktails Daniel Tofan Daniel Tofan Daniel Tofan Follow Dec 29 '25 I Asked AI to Invent 54 Cocktails # ai # webdev # creative # machinelearning 1 reaction Comments 3 comments 6 min read FACET Manifesto rokoss21 rokoss21 rokoss21 Follow Dec 16 '25 FACET Manifesto # webdev # programming # ai # architecture Comments Add Comment 2 min read Day 10 of My Web Dev Journey — Mastering CSS Positions: Absolute, Relative, Fixed & Sticky bblackwind bblackwind bblackwind Follow Dec 17 '25 Day 10 of My Web Dev Journey — Mastering CSS Positions: Absolute, Relative, Fixed & Sticky # webdev # programming # css # frontend Comments Add Comment 3 min read GeoJSON & TopoJSON Maps of Indonesia (38 Provinces) Deny Herianto Deny Herianto Deny Herianto Follow Dec 17 '25 GeoJSON & TopoJSON Maps of Indonesia (38 Provinces) # webdev # javascript # performance # resources 1 reaction Comments 1 comment 2 min read This message will self-destruct in 5 seconds... Rolan Lobo Rolan Lobo Rolan Lobo Follow Dec 16 '25 This message will self-destruct in 5 seconds... # showdev # security # webdev # productivity Comments Add Comment 6 min read Escaping Dependency Hell: How I Migrated a Legacy CRA App to React 19 & Vite Imamul Islam Ifti Imamul Islam Ifti Imamul Islam Ifti Follow Dec 16 '25 Escaping Dependency Hell: How I Migrated a Legacy CRA App to React 19 & Vite # react # vite # webdev # refactoring Comments Add Comment 7 min read Supercharge Your Web Dev Game with MCP - Part 2: Chrome DevTools MCP + AI-Driven Web Performance Susanna Wong Susanna Wong Susanna Wong Follow Dec 30 '25 Supercharge Your Web Dev Game with MCP - Part 2: Chrome DevTools MCP + AI-Driven Web Performance # webdev # ai # programming # productivity 1 reaction Comments Add Comment 7 min read I built a tool to generate relationship-aware test data for Database (no seed scripts) Dhanmoni Nath Dhanmoni Nath Dhanmoni Nath Follow Dec 17 '25 I built a tool to generate relationship-aware test data for Database (no seed scripts) # webdev # devtool # database # tooling 2 reactions Comments 3 comments 2 min read 6 Common Mistakes Teams Make in Negative Testing Arjun Sharma Arjun Sharma Arjun Sharma Follow Dec 30 '25 6 Common Mistakes Teams Make in Negative Testing # webdev # qasource # testing # negativetesting Comments 1 comment 4 min read When JavaScript Proxies Actually Save the Day Fedar Haponenka Fedar Haponenka Fedar Haponenka Follow Dec 16 '25 When JavaScript Proxies Actually Save the Day # javascript # webdev # programming # learning Comments Add Comment 3 min read Just shipped preview mode Aykut Önen Aykut Önen Aykut Önen Follow Dec 20 '25 Just shipped preview mode # news # webdev # product # ux Comments 3 comments 1 min read I Stopped Calling LLMs "Stochastic Parrots" After This Debugging Session Edward Burton Edward Burton Edward Burton Follow Dec 16 '25 I Stopped Calling LLMs "Stochastic Parrots" After This Debugging Session # webdev # programming # ai 1 reaction Comments Add Comment 3 min read Quick CRM Integrations with Retell AI's No-Code Tools: My Experience CallStack Tech CallStack Tech CallStack Tech Follow Dec 16 '25 Quick CRM Integrations with Retell AI's No-Code Tools: My Experience # ai # voicetech # machinelearning # webdev Comments Add Comment 14 min read Why CSS Classes Don’t Work with dangerouslySetInnerHTML in Next.js (and How to Fix It) Zain Muhammad Zain Muhammad Zain Muhammad Follow Dec 16 '25 Why CSS Classes Don’t Work with dangerouslySetInnerHTML in Next.js (and How to Fix It) # nextjs # react # css # webdev Comments Add Comment 1 min read I built an AI tool that turns goals into printable visual guides 妙妙 妙妙 妙妙 Follow Dec 17 '25 I built an AI tool that turns goals into printable visual guides # webdev # beginners # saas # productivity Comments Add Comment 1 min read I built a fan site for Where Winds Meet (燕云十六声) in a weekend 妙妙 妙妙 妙妙 Follow Dec 17 '25 I built a fan site for Where Winds Meet (燕云十六声) in a weekend # webdev # nextjs # gamedev # sideprojects Comments Add Comment 1 min read Made a guide site for The Last Caretaker - my first game fan site 妙妙 妙妙 妙妙 Follow Dec 17 '25 Made a guide site for The Last Caretaker - my first game fan site # webdev # javascript # beginners # gamedev Comments Add Comment 1 min read Microsoft Agent Framework with Ollama (.NET/C#) Thang Chung Thang Chung Thang Chung Follow Dec 31 '25 Microsoft Agent Framework with Ollama (.NET/C#) # webdev # agents # ai # softwareengineering 1 reaction Comments Add Comment 5 min read Website Blocked by ISP? Here’s How to Check (and Fix It) Nemanja F. Nemanja F. Nemanja F. Follow Dec 16 '25 Website Blocked by ISP? Here’s How to Check (and Fix It) # programming # webdev # isp # blocked Comments Add Comment 4 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:25 |
https://www.facebook.com/help/568137493302217 | 광고 파트너가 제공한 내 활동 정보에 따라 Facebook 광고가 표시되는 방식 조정하기 | Facebook 고객 센터 {"require":[["ScheduledServerJSWithCSS","handle",null,[{"__bbox":{"define":[["cr:11880",["CometLogoutHandler.react"],{"__rc":["CometLogoutHandler.react",null]},-1],["cr:334",["ghlTestUBTFacebook"],{"__rc":["ghlTestUBTFacebook",null]},-1],["cr:1543261",[],{"__rc":[null,null]},-1],["cr:8828",[],{"__rc":[null,null]},-1],["cr:1094907",[],{"__rc":[null,null]},-1],["cr:19583",["CometRouteActorToasterBlocklistJSModuleWrapper"],{"__rc":["CometRouteActorToasterBlocklistJSModuleWrapper",null]},-1],["cr:2718",[],{"__rc":[null,null]},-1],["cr:6943",["EventListenerImplForCacheStorage"],{"__rc":["EventListenerImplForCacheStorage",null]},-1],["cr:17080",["CometNetworkStatusToast"],{"__rc":["CometNetworkStatusToast",null]},-1],["cr:22915",[],{"__rc":[null,null]},-1],["cr:1201738",[],{"__rc":[null,null]},-1],["cr:1332233",[],{"__rc":[null,null]},-1],["cr:1345969",["AccessibilityWebAssistiveTechTypedLoggerLite"],{"__rc":["AccessibilityWebAssistiveTechTypedLoggerLite",null]},-1],["cr:1516609",["BDCometSignalCollectionTrigger"],{"__rc":["BDCometSignalCollectionTrigger",null]},-1],["cr:1634616",["CometUserActivity"],{"__rc":["CometUserActivity",null]},-1],["cr:5579",[],{"__rc":[null,null]},-1],["cr:8470",[],{"__rc":[null,null]},-1],["cr:11348",[],{"__rc":[null,null]},-1],["cr:13618",[],{"__rc":[null,null]},-1],["cr:13902",[],{"__rc":[null,null]},-1],["cr:13903",[],{"__rc":[null,null]},-1],["cr:14182",[],{"__rc":[null,null]},-1],["cr:27482",["AutoLoggingComponentValidatorListSitevarConfigJSModuleWrapper"],{"__rc":["AutoLoggingComponentValidatorListSitevarConfigJSModuleWrapper",null]},-1],["cr:133",["CometPressable.react"],{"__rc":["CometPressable.react",null]},-1],["cr:160",["MessengerWebUXLoggerImpl"],{"__rc":["MessengerWebUXLoggerImpl",null]},-1],["cr:244",["CometEmoji.react"],{"__rc":["CometEmoji.react",null]},-1],["cr:268",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:293",["LexicalHistoryPlugin.prod"],{"__rc":["LexicalHistoryPlugin.prod",null]},-1],["cr:323",[],{"__rc":[null,null]},-1],["cr:332",[],{"__rc":[null,null]},-1],["cr:370",["Lexical.prod"],{"__rc":["Lexical.prod",null]},-1],["cr:509",["LexicalComposerContext.prod"],{"__rc":["LexicalComposerContext.prod",null]},-1],["cr:804",["CometColumn.react"],{"__rc":["CometColumn.react",null]},-1],["cr:820",[],{"__rc":[null,null]},-1],["cr:824",["FDSTooltipGroup.react"],{"__rc":["FDSTooltipGroup.react",null]},-1],["cr:842",[],{"__rc":[null,null]},-1],["cr:877",["MWPThreadThemeQuery"],{"__rc":["MWPThreadThemeQuery",null]},-1],["cr:886",["useEmptyFunction"],{"__rc":["useEmptyFunction",null]},-1],["cr:895",[],{"__rc":[null,null]},-1],["cr:998",[],{"__rc":[null,null]},-1],["cr:1000",[],{"__rc":[null,null]},-1],["cr:1005",[],{"__rc":[null,null]},-1],["cr:1027",[],{"__rc":[null,null]},-1],["cr:1088",[],{"__rc":[null,null]},-1],["cr:1261",[],{"__rc":[null,null]},-1],["cr:1339",["CometToastDeferred"],{"__rc":["CometToastDeferred",null]},-1],["cr:1350",["CometColumnItem.react"],{"__rc":["CometColumnItem.react",null]},-1],["cr:1501",[],{"__rc":[null,null]},-1],["cr:1669",[],{"__rc":[null,null]},-1],["cr:1670",[],{"__rc":[null,null]},-1],["cr:1798",["FBLikeSvgIcon.react"],{"__rc":["FBLikeSvgIcon.react",null]},-1],["cr:2004",[],{"__rc":[null,null]},-1],["cr:2058",[],{"__rc":[null,null]},-1],["cr:2075",[],{"__rc":[null,null]},-1],["cr:2151",[],{"__rc":[null,null]},-1],["cr:2181",["LexicalText.prod"],{"__rc":["LexicalText.prod",null]},-1],["cr:2203",[],{"__rc":[null,null]},-1],["cr:2260",["LexicalErrorBoundary.prod"],{"__rc":["LexicalErrorBoundary.prod",null]},-1],["cr:2472",[],{"__rc":[null,null]},-1],["cr:2483",["LexicalContentEditable.prod"],{"__rc":["LexicalContentEditable.prod",null]},-1],["cr:2559",["LexicalPlainTextPlugin"],{"__rc":["LexicalPlainTextPlugin",null]},-1],["cr:2580",["logMessengerWebFalcoEvent"],{"__rc":["logMessengerWebFalcoEvent",null]},-1],["cr:2667",["CometRow.react"],{"__rc":["CometRow.react",null]},-1],["cr:2691",[],{"__rc":[null,null]},-1],["cr:2774",["LexicalUtils.prod"],{"__rc":["LexicalUtils.prod",null]},-1],["cr:2809",["TetraMWChatComposerIcons.react"],{"__rc":["TetraMWChatComposerIcons.react",null]},-1],["cr:2838",[],{"__rc":[null,null]},-1],["cr:2922",[],{"__rc":[null,null]},-1],["cr:3078",[],{"__rc":[null,null]},-1],["cr:3083",["CometRowItem.react"],{"__rc":["CometRowItem.react",null]},-1],["cr:3084",[],{"__rc":[null,null]},-1],["cr:3411",[],{"__rc":[null,null]},-1],["cr:3542",[],{"__rc":[null,null]},-1],["cr:3890",["MWChatMessengerReactionsUtils"],{"__rc":["MWChatMessengerReactionsUtils",null]},-1],["cr:4031",["MWPHandleNativeTask"],{"__rc":["MWPHandleNativeTask",null]},-1],["cr:4067",["FDSGlimmer.react"],{"__rc":["FDSGlimmer.react",null]},-1],["cr:4125",["FDSMWMessageDeliveryStatusIcons.react"],{"__rc":["FDSMWMessageDeliveryStatusIcons.react",null]},-1],["cr:4128",["MessengerDefaultTheme"],{"__rc":["MessengerDefaultTheme",null]},-1],["cr:4183",[],{"__rc":[null,null]},-1],["cr:4346",["FDSDeferredPopoverTrigger.react"],{"__rc":["FDSDeferredPopoverTrigger.react",null]},-1],["cr:4379",[],{"__rc":[null,null]},-1],["cr:4509",["MWMessageListProtectedMedia.react"],{"__rc":["MWMessageListProtectedMedia.react",null]},-1],["cr:4755",["FDSEntryPointPopoverTrigger.react"],{"__rc":["FDSEntryPointPopoverTrigger.react",null]},-1],["cr:4790",[],{"__rc":[null,null]},-1],["cr:4853",[],{"__rc":[null,null]},-1],["cr:5028",[],{"__rc":[null,null]},-1],["cr:5083",["LSPlatformRealtimeTransportEager"],{"__rc":["LSPlatformRealtimeTransportEager",null]},-1],["cr:5671",["CometTextWithEntities.react"],{"__rc":["CometTextWithEntities.react",null]},-1],["cr:5710",[],{"__rc":[null,null]},-1],["cr:5835",["useCometEntryPointDialog"],{"__rc":["useCometEntryPointDialog",null]},-1],["cr:5867",[],{"__rc":[null,null]},-1],["cr:5970",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:6023",["FDSLink.react"],{"__rc":["FDSLink.react",null]},-1],["cr:6044",["LSPlatformTaskSystemTransportEager"],{"__rc":["LSPlatformTaskSystemTransportEager",null]},-1],["cr:6057",["XComposerPhotoUploaderImmediate"],{"__rc":["XComposerPhotoUploaderImmediate","Aa4ZiMSq8w3k6SSvr8OwpAnsiTnwJNSVmzS3XFjsPX9Yvbh6gG7BrOBBkHtDZJaxi3WVYvLrUvZeXwNkZ8qBfnqa_hrkdHjE9UxA-ngh0DH6Cvbl9F0Yx7pknq_rQDRJbWAkW_dXZPLFuAA"]},-1],["cr:6194",[],{"__rc":[null,null]},-1],["cr:6221",[],{"__rc":[null,null]},-1],["cr:6542",["LSDatascriptEvaluatorMaybeEagerly"],{"__rc":["LSDatascriptEvaluatorMaybeEagerly",null]},-1],["cr:6570",["FDSIcon.react"],{"__rc":["FDSIcon.react",null]},-1],["cr:6600",["MAWBundleResource"],{"__rc":["MAWBundleResource",null]},-1],["cr:6665",[],{"__rc":[null,null]},-1],["cr:6668",[],{"__rc":[null,null]},-1],["cr:6681",[],{"__rc":[null,null]},-1],["cr:6682",["CometImage.react"],{"__rc":["CometImage.react",null]},-1],["cr:6725",["FDSTextPairing.react"],{"__rc":["FDSTextPairing.react",null]},-1],["cr:6873",[],{"__rc":[null,null]},-1],["cr:6985",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:6998",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:6999",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:7005",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:7101",[],{"__rc":[null,null]},-1],["cr:7121",[],{"__rc":[null,null]},-1],["cr:7125",[],{"__rc":[null,"Aa55c-gcIdCa2bj_Asu2RvYDzWj4RC5k0tY7vmzgzN2wrxxnQMjAoqyignOY_Rsy5WhjGF68q6Gu_eyHhzIxvcD9LyobugbPAhRI5CiJZ68_SZeMx2tjpoauVA"]},-1],["cr:7154",[],{"__rc":[null,null]},-1],["cr:7187",[],{"__rc":[null,null]},-1],["cr:7349",[],{"__rc":[null,null]},-1],["cr:7350",[],{"__rc":[null,null]},-1],["cr:7492",["FDSText.react"],{"__rc":["FDSText.react",null]},-1],["cr:7510",["FDSCircleButton.react"],{"__rc":["FDSCircleButton.react",null]},-1],["cr:7528",["MWPlatformTaskSystemEager"],{"__rc":["MWPlatformTaskSystemEager",null]},-1],["cr:7542",[],{"__rc":[null,null]},-1],["cr:8131",[],{"__rc":[null,null]},-1],["cr:8235",["FDSPopoverLoadingState.react"],{"__rc":["FDSPopoverLoadingState.react",null]},-1],["cr:8525",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:8602",["CometTooltip_DEPRECATED.react"],{"__rc":["CometTooltip_DEPRECATED.react",null]},-1],["cr:8610",["FDSLazyPopoverTrigger.react"],{"__rc":["FDSLazyPopoverTrigger.react",null]},-1],["cr:8709",[],{"__rc":[null,null]},-1],["cr:8879",[],{"__rc":[null,null]},-1],["cr:8931",["FDSProgressRingIndeterminate.react"],{"__rc":["FDSProgressRingIndeterminate.react",null]},-1],["cr:9378",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:9379",[],{"__rc":[null,null]},-1],["cr:9759",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:9775",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:9776",["MWV2ReplyButtonImpl.react"],{"__rc":["MWV2ReplyButtonImpl.react",null]},-1],["cr:9778",[],{"__rc":[null,"Aa4ZnMU9LzRZNXuY2wsDpGFeaf_2Kwu3w1YRpALL4TWTU0OVuAXhJkarB58kD0pkV8ZBD-0LtsH3mAReuVvgaM8rcj0YuV_eV3fLYxKUlAwjbIsghapGH5deig"]},-1],["cr:9780",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:9909",["FDSDialogLoadingState.react"],{"__rc":["FDSDialogLoadingState.react",null]},-1],["cr:10018",[],{"__rc":[null,null]},-1],["cr:10049",[],{"__rc":[null,null]},-1],["cr:10191",[],{"__rc":[null,null]},-1],["cr:10389",["MDSGlimmerImpl.react"],{"__rc":["MDSGlimmerImpl.react",null]},-1],["cr:10773",[],{"__rc":[null,null]},-1],["cr:11486",["MWCommandsComposerPlugin.react"],{"__rc":["MWCommandsComposerPlugin.react",null]},-1],["cr:11494",["MWCommandsComposerPluginTextNode"],{"__rc":["MWCommandsComposerPluginTextNode",null]},-1],["cr:11506",[],{"__rc":[null,null]},-1],["cr:12043",["MWInboxFollowUps"],{"__rc":["MWInboxFollowUps",null]},-1],["cr:12497",[],{"__rc":[null,null]},-1],["cr:13566",[],{"__rc":[null,null]},-1],["cr:13757",["MWV2ChatVideo.react"],{"__rc":["MWV2ChatVideo.react","Aa6l6qv9C91ERyoHk6K2UQTH1cWDn2WFxeQnKfxt3eTl1yziW7uve1SDIrFQrJ3v5ZWUc3OCOu-gIWaOuaeSegCKfYBIJryv7ZBFPdHludeZ2x8B5AeAbFfc5A"]},-1],["cr:13997",["FDSDocumentFilled16PNGIcon.react"],{"__rc":["FDSDocumentFilled16PNGIcon.react",null]},-1],["cr:14048",["FDSMessagesQuestionFilled16PNGIcon.react"],{"__rc":["FDSMessagesQuestionFilled16PNGIcon.react",null]},-1],["cr:14486",["FDSBadgeCheckmarkFilled16PNGIcon.react"],{"__rc":["FDSBadgeCheckmarkFilled16PNGIcon.react",null]},-1],["cr:15400",["FDSPhotoAddFilled24PNGIcon.react"],{"__rc":["FDSPhotoAddFilled24PNGIcon.react",null]},-1],["cr:17206",[],{"__rc":[null,null]},-1],["cr:19816",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:19893",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:19894",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:21392",["SupportAISitevarConfigJSModuleWrapper"],{"__rc":["SupportAISitevarConfigJSModuleWrapper",null]},-1],["cr:22172",["MWFDSAccount.svg.react"],{"__rc":["MWFDSAccount.svg.react",null]},-1],["cr:22216",["MWFDSBadgeCheckmark.svg.react"],{"__rc":["MWFDSBadgeCheckmark.svg.react",null]},-1],["cr:22232",["MWFDSBot.svg.react"],{"__rc":["MWFDSBot.svg.react",null]},-1],["cr:22257",["MWFDSCautionTriangle.svg.react"],{"__rc":["MWFDSCautionTriangle.svg.react",null]},-1],["cr:22288",["MWFDSCross.svg.react"],{"__rc":["MWFDSCross.svg.react",null]},-1],["cr:22300",["MWFDSDots3Vertical.svg.react"],{"__rc":["MWFDSDots3Vertical.svg.react",null]},-1],["cr:22309",["MWFDSExclamationMarkCircle.svg.react"],{"__rc":["MWFDSExclamationMarkCircle.svg.react",null]},-1],["cr:22310",["MWFDSEyeCross.svg.react"],{"__rc":["MWFDSEyeCross.svg.react",null]},-1],["cr:22312",["MWFDSFaceHappyOutline.svg.react"],{"__rc":["MWFDSFaceHappyOutline.svg.react",null]},-1],["cr:22360",["MWFDSGroup.svg.react"],{"__rc":["MWFDSGroup.svg.react",null]},-1],["cr:22362",["MWFDSHd.svg.react"],{"__rc":["MWFDSHd.svg.react",null]},-1],["cr:22371",["MWFDSInfoCircle.svg.react"],{"__rc":["MWFDSInfoCircle.svg.react",null]},-1],["cr:22421",["MWFDSPause.svg.react"],{"__rc":["MWFDSPause.svg.react",null]},-1],["cr:22437",["MWFDSPlay.svg.react"],{"__rc":["MWFDSPlay.svg.react",null]},-1],["cr:22457",["MWFDSRefreshAlt.svg.react"],{"__rc":["MWFDSRefreshAlt.svg.react",null]},-1],["cr:22459",["MWFDSReplay.svg.react"],{"__rc":["MWFDSReplay.svg.react",null]},-1],["cr:22483",["MWFDSShare.svg.react"],{"__rc":["MWFDSShare.svg.react",null]},-1],["cr:22515",["MWFDSThread.svg.react"],{"__rc":["MWFDSThread.svg.react",null]},-1],["cr:23171",["MWXMAAttachmentImpl.react"],{"__rc":["MWXMAAttachmentImpl.react","Aa6l6qv9C91ERyoHk6K2UQTH1cWDn2WFxeQnKfxt3eTl1yziW7uve1SDIrFQrJ3v5ZWUc3OCOu-gIWaOuaeSegCKfYBIJryv7ZBFPdHludeZ2x8B5AeAbFfc5A"]},-1],["cr:27633",["UFICommentFileInputAcceptValuesJSModuleWrapper"],{"__rc":["UFICommentFileInputAcceptValuesJSModuleWrapper",null]},-1],["cr:1080422",[],{"__rc":[null,null]},-1],["cr:1408565",[],{"__rc":[null,null]},-1],["cr:3024",[],{"__rc":[null,null]},-1],["cr:2046346",[],{"__rc":[null,"Aa5BfQQKxxQCTnmqVv3eGdRwOrKejs-bI5sFp66R40dOw8VdnW0G0vnp1eot-Wts5tlsluagrSCIqK28hTxsDvRYxGB51tKs80Vhzf7TRCOCttmSI45Ex3xT0w"]},-1],["cr:8710",["HelpCenterLocalePopoverQuery$Parameters.facebook"],{"__rc":["HelpCenterLocalePopoverQuery$Parameters.facebook",null]},-1],["cr:14118",["FDSInternetOutline20PNGIcon.react"],{"__rc":["FDSInternetOutline20PNGIcon.react",null]},-1],["cr:14251",["FDSTriangleDownFilled20PNGIcon.react"],{"__rc":["FDSTriangleDownFilled20PNGIcon.react",null]},-1],["WebDevicePerfInfoData",[],{"needsFullUpdate":true,"needsPartialUpdate":false,"shouldLogResourcePerf":false},3977],["WebStorageMonsterLoggingURI",[],{"uri":"\/ajax\/webstorage\/process_keys\/?state=1"},3032],["WAMediaWasmWorkerResource",[],{"url":"https:\/\/static.xx.fbcdn.net\/rsrc.php\/v4\/yi\/r\/8WvuMR4rdmn.js","name":"WAMediaWasmWorkerBundle","dynamicModules":{"IntlCurrentLocale":{"code":"ko_KR"},"ServerNonce":{"ServerNonce":"jFi5hZlrABloz316qM9Zvi"},"SiteData":{"server_revision":1031920881,"client_revision":1031920881,"push_phase":"C3","pkg_cohort":"HYP:comet_plat_default_pkg","haste_session":"20466.HYP:comet_plat_default_pkg.2.1...0","pr":1,"manifest_base_uri":"https:\/\/static.xx.fbcdn.net","manifest_origin":null,"manifest_version_prefix":null,"be_one_ahead":true,"is_rtl":false,"is_experimental_tier":false,"is_jit_warmed_up":true,"hsi":"7594765333626898708","semr_host_bucket":"6","bl_hash_version":2,"comet_env":59,"wbloks_env":false,"ef_page":"FBHelpCenterContentPageRoute","compose_bootloads":false,"spin":4,"__spin_r":1031920881,"__spin_b":"trunk","__spin_t":1768294101,"vip":"57.144.188.1"},"InitialCookieConsent":{"deferCookies":false,"initialConsent":[1,2],"noCookies":false,"shouldShowCookieBanner":false,"shouldWaitForDeferredDatrCookie":true,"optedInIntegrations":["adobe_marketo_rest_api","brightedge","chili_piper_api","cloudfront_cdn","giphy_media","google_ads_pixel_frame_legacy","google_ads_pixel_img_legacy","google_ads_pixel_legacy","google_ads_remarketing_tag","google_ads_services","google_analytics_4_tag","google_apis","google_cached_img","google_double_click_loading","google_double_click_redirecting","google_double_click_uri_connect","google_double_click_uri_frame","google_double_click_uri_img","google_fonts","google_fonts_font","google_img","google_maps","google_paid_ads_frame","google_paid_ads_img","google_tag","google_translate","google_universal_analytics_legacy","google_universal_analytics_legacy_img","google_universal_analytics_legacy_script","google_uri_frame","google_uri_script","jio","linkedin_insight","linkedin_insight_img","mapbox_maps_api","medallia_digital_experience_analytics","nytimes_oembed","reachtheworld_s3","salesforce_mcp_beacon","soundcloud_oembed","spotify_oembed","spreaker_oembed","ted_oembed","tenor_api","tenor_images","tenor_media","tiktok_oembed","twitter_analytics_pixel","twitter_analytics_pixel_img","twitter_legacy_embed","vimeo_oembed","youtube_embed","youtube_oembed","advertiser_hosted_pixel","airbus_sat","amazon_media","apps_for_office","arkose_captcha","aspnet_cdn","autodesk_fusion","bing_maps","bing_widget","boku_wallet","bootstrap","box","cardinal_centinel_api","chromecast_extensions","cloudflare_cdnjs","cloudflare_datatables","cloudflare_relay","conversions_api_gateway","demandbase_api","digitalglobe_maps_api","dlocal","dropbox","esri_sat","facebook_sdk","fastly_relay","gmg_pulse_embed_iframe","google_ads_conversions_tag","google_drive","google_fonts_legacy","google_hosted_libraries","google_oauth_api","google_oauth_api_v2","google_recaptcha","here_map_ext","hive_streaming_video","iproov","isptoolbox","jquery","js_delivr","kbank","mathjax","meshy","meta_pixel","metacdn","microsoft_excel","microsoft_office_addin","microsoft_onedrive","microsoft_speech","microsoft_teams","mmi_tiles","oculus","open_street_map","paypal_billing_agreement","paypal_fastlane_sdk","paypal_oauth_api","payu","payu_india","plaid","platformized_adyen_checkout","plotly","pydata","razorpay","recruitics","rstudio","salesforce_lighting","shopify_app_bridge","stripe","team_center","tripshot","trustly_direct_debit_ach","turbo_gala","twilio_voice","unifier","unpkg","unsplash_api","unsplash_image_loading","vega","whatsapp_arkose_captcha","yoti_api","youtube_oembed_api"],"hasGranularThirdPartyCookieConsent":true,"exemptedIntegrations":["advertiser_hosted_pixel","airbus_sat","amazon_media","apps_for_office","arkose_captcha","aspnet_cdn","autodesk_fusion","bing_maps","bing_widget","boku_wallet","bootstrap","box","cardinal_centinel_api","chromecast_extensions","cloudflare_cdnjs","cloudflare_datatables","cloudflare_relay","conversions_api_gateway","demandbase_api","digitalglobe_maps_api","dlocal","dropbox","esri_sat","facebook_sdk","fastly_relay","gmg_pulse_embed_iframe","google_ads_conversions_tag","google_drive","google_fonts_legacy","google_hosted_libraries","google_oauth_api","google_oauth_api_v2","google_recaptcha","here_map_ext","hive_streaming_video","iproov","isptoolbox","jquery","js_delivr","kbank","mathjax","meshy","meta_pixel","metacdn","microsoft_excel","microsoft_office_addin","microsoft_onedrive","microsoft_speech","microsoft_teams","mmi_tiles","oculus","open_street_map","paypal_billing_agreement","paypal_fastlane_sdk","paypal_oauth_api","payu","payu_india","plaid","platformized_adyen_checkout","plotly","pydata","razorpay","recruitics","rstudio","salesforce_lighting","shopify_app_bridge","stripe","team_center","tripshot","trustly_direct_debit_ach","turbo_gala","twilio_voice","unifier","unpkg","unsplash_api","unsplash_image_loading","vega","whatsapp_arkose_captcha","yoti_api","youtube_oembed_api"],"nonBlockingBannerPage":true,"consentRequiredForMetaPixel":false},"AnalyticsCoreData":{"device_id":"$^|Acazcr25DRPo2__oJ8np8WbQ67wMy88FFeYPhkhc7r6B2HGSjnejyC8y5kstL3_pHz66yErXvBICqwukocjliufaKxUP|fd.AcZrST89gQ7zWS8zPeZLsX8zEB1KZ_IYlR3zBnkZJpQP5MwDUHtZRMI1qjGxw-WK2akbWN7aOuQ4uUOainetsQ0J","app_id":"2220391788200892","app_version":"1031.920.881.0 (1031920881)","enable_bladerunner":false,"enable_ack":true,"push_phase":"C3","enable_observer":false,"enable_cmcd_observer":false,"enable_dataloss_timer":false,"enable_fallback_for_br":true,"queue_activation_experiment":false,"max_delay_br_queue":60000,"max_delay_br_queue_immediate":3,"max_delay_br_init_not_complete":3000,"consents":{},"app_universe":1,"br_stateful_migration_on":true,"enable_non_fb_br_stateless_by_default":false,"use_falco_as_mutex_key":false,"is_intern":false},"ServerTimeData":{"serverTime":1768294102125,"timeOfRequestStart":1768294101966.5,"timeOfResponseStart":1768294102066.4},"cr:310":{"__bbox":{"__rc":["RunWWW",null]}},"cr:686":{"__bbox":{"__rc":["FlipperPluginsManager",null]}},"cr:1126":{"__bbox":{"__rc":["TimeSliceSham",null]}},"cr:3725":{"__bbox":{"__rc":["clearTimeoutSW",null]}},"cr:4344":{"__bbox":{"__rc":["setTimeoutSW",null]}},"cr:6640":{"__bbox":{"__rc":[null,null]}},"cr:6895":{"__bbox":{"__rc":["cometAsyncRequestHeaders",null]}},"cr:8958":{"__bbox":{"__rc":["FBJSON",null]}},"cr:12180":{"__bbox":{"__rc":["QPLUserTimingPlugin",null]}},"cr:13925":{"__bbox":{"__rc":["VideoTranscodeToMp4",null]}},"cr:925100":{"__bbox":{"__rc":["RunComet",null]}},"cr:1752405":{"__bbox":{"__rc":["QPLAddCometRequestHeaders",null]}},"cr:1984081":{"__bbox":{"__rc":["QPLSapienzPlugin",null]}}},"hsdp":{"bxData":{"237":{"uri":"https:\/\/static.xx.fbcdn.net\/rsrc.php\/yR\/r\/ayqr5HQtlkb.wasm"},"6946":{"uri":"https:\/\/static.xx.fbcdn.net\/rsrc.php\/yf\/r\/rogm88TRRiw.wasm"},"31390":{"uri":"https:\/\/static.xx.fbcdn.net\/rsrc.php\/yl\/r\/php8T1oSIZM.wasm"},"33861":{"uri":"https:\/\/static.xx.fbcdn.net\/rsrc.php\/yj\/r\/wP_Nd8029HG.wasm"}},"clpData":{"1744178":{"r":1,"s":1},"1838142":{"r":1,"s":1}},"gkxData":{"1624":{"result":false,"hash":null},"2160":{"result":false,"hash":null},"3272":{"result":false,"hash":null},"4444":{"result":true,"hash":null},"5679":{"result":false,"hash":null},"20836":{"result":false,"hash":null},"20935":{"result":true,"hash":null},"21043":{"result":false,"hash":null},"21050":{"result":false,"hash":null},"21051":{"result":false,"hash":null},"21053":{"result":false,"hash":null},"21055":{"result":false,"hash":null},"21056":{"result":false,"hash":null},"21057":{"result":false,"hash":null},"21058":{"result":true,"hash":null}},"qplData":{"106":{},"418":{"r":1}},"justknobxData":{"168":{"r":60000},"1276":{"r":true},"2379":{"r":35000}}}},7438],["IgMsgrXacGatingManager",[],{"is_xac_enabled_for_viewer":false,"is_groups_xac_enabled_for_viewer":false},6372],["LSPlatformMessengerSyncParams",[],{"mailbox":"{\"bloks_version\":\"68d098dee84411cebd1e399c21b0b1fcec452408ecd9762ba6e4c93702f2c972\",\"full_height\":200,\"locale\":\"ko_KR\",\"preview_height\":360,\"preview_height_large\":360,\"preview_width\":480,\"preview_width_large\":480,\"scale\":1,\"snapshot_num_threads_per_page\":15}","contact":"{\"locale\":\"ko_KR\"}","e2ee":"{\"locale\":\"ko_KR\"}","communityExclusive":"{\"locale\":\"ko_KR\"}"},6729],["LSPlatformWorkplaceSyncParams",[],{"mailbox":"{\"full_height\":200,\"locale\":\"ko_KR\",\"preview_height\":200,\"preview_height_large\":400,\"preview_width\":183,\"preview_width_large\":360,\"scale\":1,\"snapshot_num_threads_per_page\":15}","contact":"{\"locale\":\"ko_KR\"}","e2ee":"{\"locale\":\"ko_KR\"}"},6730],["WAWebOpusRecorderWorkerResource",[],{"url":"https:\/\/static.xx.fbcdn.net\/rsrc.php\/v4\/yT\/r\/PRcnddXVls-.js","name":"WAWebOpusRecorderWorkerBundle","hsdp":{}},7347],["MessengerWebPrivacySettings",[],{"read_receipts_disabled":0,"e2ee_xma_previews_disabled":false,"e2ee_hd_media_enabled":false,"biim_featured_unit":1},7422],["AdsAISitevarConfig",[],{"bot_id":"1046070283321980"},7515],["WorkerConfig",[],{"worker":"shared"},7679],["MessengerWebGenAIConsentStatus",[],{"chat_consented":false,"nux_scope":"ROW","inline_disclosure_text":{"text":"Meta AI\ub97c \uc0ac\uc6a9\ud558\uba74 AI \uc57d\uad00\uc5d0 \ub3d9\uc758\ud558\uac8c \ub429\ub2c8\ub2e4. AI\uc640\uc758 \uc0c1\ud638\uc791\uc6a9\uc740 Meta\uc5d0\uc11c \uc81c\uacf5\ud558\ub294 AI \uc194\ub8e8\uc158\uc744 \uac1c\uc120\ud558\ub294 \ub370 \uc0ac\uc6a9\ub429\ub2c8\ub2e4.","ranges":[{"offset":14,"length":5,"url":"https:\/\/www.facebook.com\/legal\/ai-terms"},{"offset":42,"length":18,"url":"https:\/\/www.facebook.com\/privacy\/guide\/generative-ai"}]},"training_message_text":null},8330],["CurrentEnvironment",[],{"facebookdotcom":true,"messengerdotcom":false,"workplacedotcom":false,"instagramdotcom":false,"workdotmetadotcom":false,"horizondotmetadotcom":false,"developersdotmetadotcom":false},827],["PaddedStickerConfig",[],{},1667],["IntlCompactDecimalNumberFormatConfig",[],{"short_patterns":{"3":{"24":{"min_fraction_digits":null,"min_integer_digits":1,"positive_prefix_pattern":"","positive_suffix_pattern":"\ucc9c","negative_prefix_pattern":"-","negative_suffix_pattern":"\ucc9c"}},"4":{"24":{"min_fraction_digits":null,"min_integer_digits":1,"positive_prefix_pattern":"","positive_suffix_pattern":"\ub9cc","negative_prefix_pattern":"-","negative_suffix_pattern":"\ub9cc"}},"5":{"24":{"min_fraction_digits":null,"min_integer_digits":2,"positive_prefix_pattern":"","positive_suffix_pattern":"\ub9cc","negative_prefix_pattern":"-","negative_suffix_pattern":"\ub9cc"}},"6":{"24":{"min_fraction_digits":null,"min_integer_digits":3,"positive_prefix_pattern":"","positive_suffix_pattern":"\ub9cc","negative_prefix_pattern":"-","negative_suffix_pattern":"\ub9cc"}},"7":{"24":{"min_fraction_digits":null,"min_integer_digits":4,"positive_prefix_pattern":"","positive_suffix_pattern":"\ub9cc","negative_prefix_pattern":"-","negative_suffix_pattern":"\ub9cc"}},"8":{"24":{"min_fraction_digits":null,"min_integer_digits":1,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc5b5","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc5b5"}},"9":{"24":{"min_fraction_digits":null,"min_integer_digits":2,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc5b5","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc5b5"}},"10":{"24":{"min_fraction_digits":null,"min_integer_digits":3,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc5b5","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc5b5"}},"11":{"24":{"min_fraction_digits":null,"min_integer_digits":4,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc5b5","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc5b5"}},"12":{"24":{"min_fraction_digits":null,"min_integer_digits":1,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc870","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc870"}},"13":{"24":{"min_fraction_digits":null,"min_integer_digits":2,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc870","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc870"}},"14":{"24":{"min_fraction_digits":null,"min_integer_digits":3,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc870","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc870"}}},"long_patterns":{"3":{"24":{"min_fraction_digits":null,"min_integer_digits":1,"positive_prefix_pattern":"","positive_suffix_pattern":"\ucc9c","negative_prefix_pattern":"-","negative_suffix_pattern":"\ucc9c"}},"4":{"24":{"min_fraction_digits":null,"min_integer_digits":1,"positive_prefix_pattern":"","positive_suffix_pattern":"\ub9cc","negative_prefix_pattern":"-","negative_suffix_pattern":"\ub9cc"}},"5":{"24":{"min_fraction_digits":null,"min_integer_digits":2,"positive_prefix_pattern":"","positive_suffix_pattern":"\ub9cc","negative_prefix_pattern":"-","negative_suffix_pattern":"\ub9cc"}},"6":{"24":{"min_fraction_digits":null,"min_integer_digits":3,"positive_prefix_pattern":"","positive_suffix_pattern":"\ub9cc","negative_prefix_pattern":"-","negative_suffix_pattern":"\ub9cc"}},"7":{"24":{"min_fraction_digits":null,"min_integer_digits":4,"positive_prefix_pattern":"","positive_suffix_pattern":"\ub9cc","negative_prefix_pattern":"-","negative_suffix_pattern":"\ub9cc"}},"8":{"24":{"min_fraction_digits":null,"min_integer_digits":1,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc5b5","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc5b5"}},"9":{"24":{"min_fraction_digits":null,"min_integer_digits":2,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc5b5","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc5b5"}},"10":{"24":{"min_fraction_digits":null,"min_integer_digits":3,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc5b5","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc5b5"}},"11":{"24":{"min_fraction_digits":null,"min_integer_digits":4,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc5b5","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc5b5"}},"12":{"24":{"min_fraction_digits":null,"min_integer_digits":1,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc870","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc870"}},"13":{"24":{"min_fraction_digits":null,"min_integer_digits":2,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc870","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc870"}},"14":{"24":{"min_fraction_digits":null,"min_integer_digits":3,"positive_prefix_pattern":"","positive_suffix_pattern":"\uc870","negative_prefix_pattern":"-","negative_suffix_pattern":"\uc870"}}}},2981],["MessengerWebPresenceCookieData",[],{"cookie":""},4664],["MqttWebDeviceID",[],{"clientID":"d8b63cd7-57fe-4916-8827-395601844975"},5003],["ServerAppID",[],{"app_id":"2220391788200892"},5217],["MessengerWebRegion",[],{"regionNullable":null},5389],["MDCAutoLogging",[],{"sessionId":"124SMTTUBRHtONmks","origHttpReferrer":null,"origRequestUri":"https:\/\/www.facebook.com\/help\/568137493302217","rtwIp":"","delocalizedUrl":null},7749],["UniversalSiteAutoLoggingPlatform",[],{"is_galaxy":false},8628],["MarauderConfig",[],{"app_version":"1.0.0.0 (1031920881)","gk_enabled":false},31],["RTISubscriptionManagerConfig",[],{"config":{},"autobot":{},"assimilator":{},"unsubscribe_release":true,"bladerunner_www_sandbox":null,"is_intern":false},1081],["MqttWebConfig",[],{"fbid":"0","appID":219994525426954,"endpoint":"wss:\/\/edge-chat.facebook.com\/chat","pollingEndpoint":"https:\/\/edge-chat.facebook.com\/mqtt\/pull","subscribedTopics":[],"capabilities":10,"clientCapabilities":3,"chatVisibility":false,"hostNameOverride":""},3790],["RequestStreamE2EClientSamplingConfig",[],{"sampleRate":500000,"methodToSamplingMultiplier":{"RTCSessionMessage":10000,"Presence":0.01,"FBGQLS:VOD_TICKER_SUBSCRIBE":0.01,"FBGQLS:STORIES_TRAY_SUBSCRIBE":100,"Collabri":0.1,"FBGQLS:WORK_AVAILABILITY_STATUS_FANOUT_SUBSCRIBE":0.1,"FBGQLS:GROUP_UNSEEN_ACTIVITY_SUBSCRIBE":0.1,"FBGQLS:GROUP_RESET_UNSEEN_ACTIVITY_SUBSCRIBE":0.1,"FBGQLS:INTERN_CALENDAR_UPDATE_SUBSCRIBE":0.1,"SKY:gizmo_manage":10000,"FBGQLS:XFB_HZW_CHALLENGE_COMPLETE_SUBSCRIBE":10,"FalcoMobile":1,"FBGQLS:FEEDBACK_LIKE_SUBSCRIBE":10,"FBGQLS:HUDDLE_USERS_REQUESTED_TO_SPEAK_COUNT_SUBSCRIBE":1000}},4501],["DGWWebConfig",[],{"appId":"2220391788200892","appVersion":"0","dgwVersion":"2","endpoint":"","fbId":"0","authType":""},5508],["cr:5544",["FDSCardedDialogLegacy.react"],{"__rc":["FDSCardedDialogLegacy.react",null]},-1],["cr:6308",["FDSDialogPageLegacy.react"],{"__rc":["FDSDialogPageLegacy.react",null]},-1],["cr:12313",[],{"__rc":[null,null]},-1],["cr:22280",["MWFDSCommentLeftRight.svg.react"],{"__rc":["MWFDSCommentLeftRight.svg.react",null]},-1],["cr:22342",["MWFDSFriendGenericCheckmark.svg.react"],{"__rc":["MWFDSFriendGenericCheckmark.svg.react",null]},-1],["cr:22487",["MWFDSShield.svg.react"],{"__rc":["MWFDSShield.svg.react",null]},-1],["cr:43",["FDSListCell.react"],{"__rc":["FDSListCell.react",null]},-1],["cr:2201",[],{"__rc":[null,null]},-1],["cr:2625",[],{"__rc":[null,null]},-1],["cr:4614",["MWFDSMenuItemSparkles.svg.react"],{"__rc":["MWFDSMenuItemSparkles.svg.react",null]},-1],["cr:7379",["CometTheme.react"],{"__rc":["CometTheme.react",null]},-1],["cr:7380",[],{"__rc":[null,null]},-1],["cr:10054",["FDSButton.react"],{"__rc":["FDSButton.react",null]},-1],["cr:321",[],{"__rc":[null,null]},-1],["cr:6923",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:8697",["FDSListCellPressable.react"],{"__rc":["FDSListCellPressable.react",null]},-1],["cr:22205",["MWFDSAudioOff.svg.react"],{"__rc":["MWFDSAudioOff.svg.react",null]},-1],["cr:22358",["MWFDSGroupBlock.svg.react"],{"__rc":["MWFDSGroupBlock.svg.react",null]},-1],["cr:22359",["MWFDSGroupRemove.svg.react"],{"__rc":["MWFDSGroupRemove.svg.react",null]},-1],["cr:22698",["MWFDSMenuItemGroupRemove.svg.react"],{"__rc":["MWFDSMenuItemGroupRemove.svg.react",null]},-1],["cr:112",[],{"__rc":[null,null]},-1],["cr:227",[],{"__rc":[null,null]},-1],["cr:620",["FDSPopover.react"],{"__rc":["FDSPopover.react",null]},-1],["cr:739",["LexicalPlainTextPlugin.prod"],{"__rc":["LexicalPlainTextPlugin.prod",null]},-1],["cr:1042",["XAsyncRequestWWW"],{"__rc":["XAsyncRequestWWW",null]},-1],["cr:1113",["useMessengerWebThreadImpressionLogging"],{"__rc":["useMessengerWebThreadImpressionLogging",null]},-1],["cr:1600",[],{"__rc":[null,null]},-1],["cr:2457",[],{"__rc":[null,null]},-1],["cr:2466",["FDSMenuItem.react"],{"__rc":["FDSMenuItem.react",null]},-1],["cr:2673",["MWPUseVoiceRecorderV2"],{"__rc":["MWPUseVoiceRecorderV2",null]},-1],["cr:2884",[],{"__rc":[null,null]},-1],["cr:2998",["CometIXTFacebookProactiveWarningFlowTriggerEntryPoint.entrypoint"],{"__rc":["CometIXTFacebookProactiveWarningFlowTriggerEntryPoint.entrypoint",null]},-1],["cr:3116",["useCometEntryPointDialog"],{"__rc":["useCometEntryPointDialog",null]},-1],["cr:3237",["TetraMWChatComposerOverflowIcons.react"],{"__rc":["TetraMWChatComposerOverflowIcons.react",null]},-1],["cr:3449",["ReStoreLocalStorageQuotaExceed"],{"__rc":["ReStoreLocalStorageQuotaExceed",null]},-1],["cr:3907",[],{"__rc":[null,null]},-1],["cr:3912",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:4186",[],{"__rc":[null,null]},-1],["cr:4318",[],{"__rc":[null,null]},-1],["cr:4426",["MWFDSChatHeaderDetailsSubtitleMutedIcon.react"],{"__rc":["MWFDSChatHeaderDetailsSubtitleMutedIcon.react",null]},-1],["cr:4703",["MWInboxHeaderPublicChatSubText.react"],{"__rc":["MWInboxHeaderPublicChatSubText.react",null]},-1],["cr:4707",["CometEmoji.react"],{"__rc":["CometEmoji.react",null]},-1],["cr:4723",["MWPublicChatMemberRequestsBanner.react"],{"__rc":["MWPublicChatMemberRequestsBanner.react",null]},-1],["cr:5483",[],{"__rc":[null,null]},-1],["cr:6106",["FDSButtonGroup.react"],{"__rc":["FDSButtonGroup.react",null]},-1],["cr:6234",["MWPAudioPlaybackContext.react"],{"__rc":["MWPAudioPlaybackContext.react",null]},-1],["cr:6285",["useThreadHasCompletedEBFrontLoadingNoop"],{"__rc":["useThreadHasCompletedEBFrontLoadingNoop",null]},-1],["cr:6941",["FDSMenu.react"],{"__rc":["FDSMenu.react",null]},-1],["cr:7905",["usePresenceUnifiedIsThreadActive"],{"__rc":["usePresenceUnifiedIsThreadActive",null]},-1],["cr:8839",[],{"__rc":[null,null]},-1],["cr:9056",[],{"__rc":[null,"Aa6hRwB1PByKaf6OUg_a2MSKWkdxhZ6zN4BtaBT82CNkr9JI7NHG0okMofqkuqPBhS7ASpwribsk2uVLgDeDz519sSyivPDnxT1WTcTCpyuZ8FmCSDvO4NpkIw"]},-1],["cr:9715",[],{"__rc":[null,null]},-1],["cr:9765",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:9772",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:9773",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:9777",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:9929",[],{"__rc":[null,null]},-1],["cr:10030",[],{"__rc":[null,null]},-1],["cr:11989",[],{"__rc":[null,"Aa5FviotpuXqtIxWEaehJAPyvps5wah0UM3aoWbrkuATUtQg_XSQzZF8Y5MIZdOE0YyHr4tMa9DugkU_5NUoUkGya2bQ1xFMEtruxYjYHSp2ovJldWqnwwAYOw"]},-1],["cr:12317",[],{"__rc":[null,"Aa7g-cAadZ_qasjdXDDGs0ZCIqkopDYLqv9cfkj8NW0eJaZYxqAbwbOVFiqqDlKFlcltMtlA06-iBDBqiIeFS66-4Fi15En52SGVFiJRjruU7GbEIoUZhTVovw"]},-1],["cr:12419",["MWEditMessageOnUpArrowPlugin.react"],{"__rc":["MWEditMessageOnUpArrowPlugin.react",null]},-1],["cr:12528",[],{"__rc":[null,null]},-1],["cr:13308",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:13469",[],{"__rc":[null,null]},-1],["cr:13992",["FDSCrossFilled12PNGIcon.react"],{"__rc":["FDSCrossFilled12PNGIcon.react",null]},-1],["cr:14853",["FDSDots3HorizontalFilled16PNGIcon.react"],{"__rc":["FDSDots3HorizontalFilled16PNGIcon.react",null]},-1],["cr:17333",[],{"__rc":[null,null]},-1],["cr:17336",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:19928",["MWContextBannerQuickActions.react"],{"__rc":["MWContextBannerQuickActions.react",null]},-1],["cr:21441",[],{"__rc":[null,null]},-1],["cr:21442",[],{"__rc":[null,null]},-1],["cr:22250",["MWFDSCamcorder.svg.react"],{"__rc":["MWFDSCamcorder.svg.react",null]},-1],["cr:22261",["MWFDSCheckmarkCircle.svg.react"],{"__rc":["MWFDSCheckmarkCircle.svg.react",null]},-1],["cr:22264",["MWFDSChevronDown.svg.react"],{"__rc":["MWFDSChevronDown.svg.react",null]},-1],["cr:22268",["MWFDSChevronRight.svg.react"],{"__rc":["MWFDSChevronRight.svg.react",null]},-1],["cr:22287",["MWFDSCrossCircle.svg.react"],{"__rc":["MWFDSCrossCircle.svg.react",null]},-1],["cr:22296",["MWFDSDocument.svg.react"],{"__rc":["MWFDSDocument.svg.react",null]},-1],["cr:22299",["MWFDSDots3Horizontal.svg.react"],{"__rc":["MWFDSDots3Horizontal.svg.react",null]},-1],["cr:22302",["MWFDSDragHandle.svg.react"],{"__rc":["MWFDSDragHandle.svg.react",null]},-1],["cr:22315",["MWFDSFaceHappy.svg.react"],{"__rc":["MWFDSFaceHappy.svg.react",null]},-1],["cr:22337",["MWFDSForwardAction.svg.react"],{"__rc":["MWFDSForwardAction.svg.react",null]},-1],["cr:22338",["MWFDSForward.svg.react"],{"__rc":["MWFDSForward.svg.react",null]},-1],["cr:22341",["MWFDSFriendGenericAdd.svg.react"],{"__rc":["MWFDSFriendGenericAdd.svg.react",null]},-1],["cr:22351",["MWFDSGif.svg.react"],{"__rc":["MWFDSGif.svg.react",null]},-1],["cr:22361",["MWFDSHdOutline.svg.react"],{"__rc":["MWFDSHdOutline.svg.react",null]},-1],["cr:22398",["MWFDSMessage.svg.react"],{"__rc":["MWFDSMessage.svg.react",null]},-1],["cr:22400",["MWFDSMicrophone.svg.react"],{"__rc":["MWFDSMicrophone.svg.react",null]},-1],["cr:22402",["MWFDSMinus.svg.react"],{"__rc":["MWFDSMinus.svg.react",null]},-1],["cr:22431",["MWFDSPhone.svg.react"],{"__rc":["MWFDSPhone.svg.react",null]},-1],["cr:22434",["MWFDSPhotoPlus.svg.react"],{"__rc":["MWFDSPhotoPlus.svg.react",null]},-1],["cr:22435",["MWFDSPhoto.svg.react"],{"__rc":["MWFDSPhoto.svg.react",null]},-1],["cr:22438",["MWFDSPlusCircle.svg.react"],{"__rc":["MWFDSPlusCircle.svg.react",null]},-1],["cr:22440",["MWFDSPoll.svg.react"],{"__rc":["MWFDSPoll.svg.react",null]},-1],["cr:22450",["MWFDSPushpin.svg.react"],{"__rc":["MWFDSPushpin.svg.react",null]},-1],["cr:22460",["MWFDSReply.svg.react"],{"__rc":["MWFDSReply.svg.react",null]},-1],["cr:22469",["MWFDSRollCall.svg.react"],{"__rc":["MWFDSRollCall.svg.react",null]},-1],["cr:22501",["MWFDSStickersFace.svg.react"],{"__rc":["MWFDSStickersFace.svg.react",null]},-1],["cr:22549",["MWFDSMenuItemArrowDown.svg.react"],{"__rc":["MWFDSMenuItemArrowDown.svg.react",null]},-1],["cr:23170",["MWXMAV2AttachmentContainerComponent.react"],{"__rc":["MWXMAV2AttachmentContainerComponent.react","Aa6l6qv9C91ERyoHk6K2UQTH1cWDn2WFxeQnKfxt3eTl1yziW7uve1SDIrFQrJ3v5ZWUc3OCOu-gIWaOuaeSegCKfYBIJryv7ZBFPdHludeZ2x8B5AeAbFfc5A"]},-1],["cr:951783",[],{"__rc":[null,null]},-1],["cr:1012418",["CometRelay"],{"__rc":["CometRelay",null]},-1],["cr:1443591",["VideoChatLinksUserActionsTypedLogger"],{"__rc":["VideoChatLinksUserActionsTypedLogger",null]},-1],["cr:73",[],{"__rc":[null,null]},-1],["cr:3020",["FDSDialog.react"],{"__rc":["FDSDialog.react",null]},-1],["cr:4220",["FDSEntityHeaderTabs.react"],{"__rc":["FDSEntityHeaderTabs.react",null]},-1],["cr:4354",[],{"__rc":[null,null]},-1],["cr:6827",[],{"__rc":[null,null]},-1],["cr:7626",["FDSDialogHeader.react"],{"__rc":["FDSDialogHeader.react",null]},-1],["cr:99",[],{"__rc":[null,null]},-1],["cr:537",["useCAALoggedOutDialogWrapperHook"],{"__rc":["useCAALoggedOutDialogWrapperHook",null]},-1],["cr:913",[],{"__rc":[null,null]},-1],["cr:1222",[],{"__rc":[null,null]},-1],["cr:1607",[],{"__rc":[null,null]},-1],["cr:2324",[],{"__rc":[null,null]},-1],["cr:2354",[],{"__rc":[null,null]},-1],["cr:3527",[],{"__rc":[null,null]},-1],["cr:4149",[],{"__rc":[null,null]},-1],["cr:5709",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:5931",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:6094",["useEmptyFunction"],{"__rc":["useEmptyFunction",null]},-1],["cr:9742",[],{"__rc":[null,null]},-1],["cr:10071",["EBLSResignCdnUrlDeferred"],{"__rc":["EBLSResignCdnUrlDeferred",null]},-1],["cr:10181",[],{"__rc":[null,null]},-1],["cr:10182",[],{"__rc":[null,null]},-1],["cr:10766",["dexie_maw-next"],{"__rc":["dexie_maw-next",null]},-1],["cr:11999",["useEmptyFunction"],{"__rc":["useEmptyFunction",null]},-1],["cr:13141",[],{"__rc":[null,null]},-1],["cr:19810",["MAWFTSThreadsRestore"],{"__rc":["MAWFTSThreadsRestore",null]},-1],["cr:20241",[],{"__rc":[null,null]},-1],["cr:21048",["WAAPIDeferred"],{"__rc":["WAAPIDeferred",null]},-1],["cr:22266",["MWFDSChevronLeft.svg.react"],{"__rc":["MWFDSChevronLeft.svg.react",null]},-1],["cr:22301",["MWFDSDownload.svg.react"],{"__rc":["MWFDSDownload.svg.react",null]},-1],["cr:921407",["useNoopDebuggingInfoComponent"],{"__rc":["useNoopDebuggingInfoComponent",null]},-1],["cr:1453865",[],{"__rc":[null,null]},-1],["cr:1680308",[],{"__rc":[null,null]},-1],["cr:1826284",["useVideoPlayerVolumeControlAudioAvailabilityUI"],{"__rc":["useVideoPlayerVolumeControlAudioAvailabilityUI",null]},-1],["cr:1875194",["useAudioAvailabilityAtPlayhead"],{"__rc":["useAudioAvailabilityAtPlayhead",null]},-1],["cr:1954434",[],{"__rc":[null,null]},-1],["cr:329",[],{"__rc":[null,null]},-1],["cr:2384",[],{"__rc":[null,null]},-1],["cr:5426",["FDSPressableFacepile.react"],{"__rc":["FDSPressableFacepile.react",null]},-1],["cr:6309",[],{"__rc":[null,null]},-1],["cr:6810",["FDSDialogPage.react"],{"__rc":["FDSDialogPage.react",null]},-1],["cr:6993",[],{"__rc":[null,null]},-1],["cr:7300",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:7741",["FDSMultiStepDialogLegacy.react"],{"__rc":["FDSMultiStepDialogLegacy.react",null]},-1],["cr:9720",["FDSDialogButtonGroupFooter.react"],{"__rc":["FDSDialogButtonGroupFooter.react",null]},-1],["cr:9761",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:12314",[],{"__rc":[null,null]},-1],["cr:13980",["FDSChevronLeftOutline20PNGIcon.react"],{"__rc":["FDSChevronLeftOutline20PNGIcon.react",null]},-1],["cr:14710",["FDSChevronRightOutline20PNGIcon.react"],{"__rc":["FDSChevronRightOutline20PNGIcon.react",null]},-1],["cr:22185",["MWFDSAppMessenger.svg.react"],{"__rc":["MWFDSAppMessenger.svg.react",null]},-1],["cr:22262",["MWFDSCheckmark.svg.react"],{"__rc":["MWFDSCheckmark.svg.react",null]},-1],["cr:22369",["MWFDSImagine.svg.react"],{"__rc":["MWFDSImagine.svg.react",null]},-1],["cr:9908",["FDSDialogLoadingState.react"],{"__rc":["FDSDialogLoadingState.react",null]},-1],["cr:744",[],{"__rc":[null,null]},-1],["cr:5976",["FDSRadio.react"],{"__rc":["FDSRadio.react",null]},-1],["cr:9774",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:874",["useEmptyFunction"],{"__rc":["useEmptyFunction","Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:9068",[],{"__rc":[null,null]},-1],["cr:22561",["MWFDSMenuItemAudioOff.svg.react"],{"__rc":["MWFDSMenuItemAudioOff.svg.react",null]},-1],["cr:22603",["MWFDSMenuItemCamcorder.svg.react"],{"__rc":["MWFDSMenuItemCamcorder.svg.react",null]},-1],["cr:22612",["MWFDSMenuItemChatHost.svg.react"],{"__rc":["MWFDSMenuItemChatHost.svg.react",null]},-1],["cr:22638",["MWFDSMenuItemCross.svg.react"],{"__rc":["MWFDSMenuItemCross.svg.react",null]},-1],["cr:22697",["MWFDSMenuItemGroupBlock.svg.react"],{"__rc":["MWFDSMenuItemGroupBlock.svg.react",null]},-1],["cr:22734",["MWFDSMenuItemMessage.svg.react"],{"__rc":["MWFDSMenuItemMessage.svg.react",null]},-1],["cr:22765",["MWFDSMenuItemPhone.svg.react"],{"__rc":["MWFDSMenuItemPhone.svg.react",null]},-1],["cr:22779",["MWFDSMenuItemProfile.svg.react"],{"__rc":["MWFDSMenuItemProfile.svg.react",null]},-1],["cr:22816",["MWFDSMenuItemShieldCheck.svg.react"],{"__rc":["MWFDSMenuItemShieldCheck.svg.react",null]},-1],["cr:22817",["MWFDSMenuItemShieldStar.svg.react"],{"__rc":["MWFDSMenuItemShieldStar.svg.react",null]},-1],["cr:13978",["FDSChevronLeftFilled16PNGIcon.react"],{"__rc":["FDSChevronLeftFilled16PNGIcon.react",null]},-1],["cr:13982",["FDSChevronRightFilled16PNGIcon.react"],{"__rc":["FDSChevronRightFilled16PNGIcon.react",null]},-1],["cr:14207",["FDSCommentFilled20PNGIcon.react"],{"__rc":["FDSCommentFilled20PNGIcon.react",null]},-1],["cr:4708",[],{"__rc":[null,null]},-1],["cr:6101",["useThrottledImpl"],{"__rc":["useThrottledImpl",null]},-1],["cr:10825",["CometEmojiDataSourceQuery.facebook.graphql"],{"__rc":["CometEmojiDataSourceQuery.facebook.graphql",null]},-1],["cr:11559",["useCometCategoriesLocalizedNameQuery.facebook.graphql"],{"__rc":["useCometCategoriesLocalizedNameQuery.facebook.graphql",null]},-1],["cr:11766",["CometEmojiPickerSearchResults_emojiQuery.facebook.graphql"],{"__rc":["CometEmojiPickerSearchResults_emojiQuery.facebook.graphql",null]},-1],["cr:13959",["FDSBulbFilled16PNGIcon.react"],{"__rc":["FDSBulbFilled16PNGIcon.react",null]},-1],["cr:14879",["FDSEmojiFilled16PNGIcon.react"],{"__rc":["FDSEmojiFilled16PNGIcon.react",null]},-1],["cr:14882",["FDSEmojiOutline16PNGIcon.react"],{"__rc":["FDSEmojiOutline16PNGIcon.react",null]},-1],["cr:14938",["FDSFlagFilled16PNGIcon.react"],{"__rc":["FDSFlagFilled16PNGIcon.react",null]},-1],["cr:15370",["FDSPawFilled16PNGIcon.react"],{"__rc":["FDSPawFilled16PNGIcon.react",null]},-1],["cr:15682",["FDSSoccerFilled16PNGIcon.react"],{"__rc":["FDSSoccerFilled16PNGIcon.react",null]},-1],["cr:21371",["FDSAppleFilled16PNGIcon.react"],{"__rc":["FDSAppleFilled16PNGIcon.react",null]},-1],["cr:21372",["FDSAtSignFilled16PNGIcon.react"],{"__rc":["FDSAtSignFilled16PNGIcon.react",null]},-1],["cr:21373",["FDSBeachFilled16PNGIcon.react"],{"__rc":["FDSBeachFilled16PNGIcon.react",null]},-1],["cr:21375",["FDSFlagOutline16PNGIcon.react"],{"__rc":["FDSFlagOutline16PNGIcon.react",null]},-1],["cr:21377",["FDSRecentsFilled16PNGIcon.react"],{"__rc":["FDSRecentsFilled16PNGIcon.react",null]},-1],["cr:22391",["MWFDSMagnifyingGlass.svg.react"],{"__rc":["MWFDSMagnifyingGlass.svg.react",null]},-1],["cr:22439",["MWFDSPlus.svg.react"],{"__rc":["MWFDSPlus.svg.react",null]},-1],["cr:294",[],{"__rc":[null,null]},-1],["cr:3817",[],{"__rc":[null,null]},-1],["cr:7267",["AdsDataAtom"],{"__rc":["AdsDataAtom",null]},-1],["cr:10110",[],{"__rc":[null,null]},-1],["cr:10217",[],{"__rc":[null,null]},-1],["cr:21215",["useEmptyFunction"],{"__rc":["useEmptyFunction",null]},-1],["cr:27641",[],{"__rc":[null,null]},-1],["cr:1641505",[],{"__rc":[null,null]},-1],["cr:22180",["MWFDSAppGroups.svg.react"],{"__rc":["MWFDSAppGroups.svg.react",null]},-1],["cr:22200",["MWFDSArrowsLeftRightCircle.svg.react"],{"__rc":["MWFDSArrowsLeftRightCircle.svg.react",null]},-1],["cr:22241",["MWFDSBusinessBriefcase.svg.react"],{"__rc":["MWFDSBusinessBriefcase.svg.react",null]},-1],["cr:22353",["MWFDSGlobeAmericas.svg.react"],{"__rc":["MWFDSGlobeAmericas.svg.react",null]},-1],["cr:22389",["MWFDSLock.svg.react"],{"__rc":["MWFDSLock.svg.react",null]},-1],["cr:22411",["MWFDSNeighborhood.svg.react"],{"__rc":["MWFDSNeighborhood.svg.react",null]},-1],["cr:22424",["MWFDSPennant.svg.react"],{"__rc":["MWFDSPennant.svg.react",null]},-1],["cr:22524",["MWFDSUnlock.svg.react"],{"__rc":["MWFDSUnlock.svg.react",null]},-1],["cr:950105",[],{"__rc":[null,null]},-1],["cr:3286",[],{"__rc":[null,null]},-1],["cr:1111",[],{"__rc":[null,null]},-1],["cr:1200",[],{"__rc":[null,null]},-1],["cr:2243",[],{"__rc":[null,null]},-1],["cr:4140",[],{"__rc":[null,null]},-1],["cr:5790",[],{"__rc":[null,null]},-1],["cr:12502",[],{"__rc":[null,null]},-1],["cr:12503",[],{"__rc":[null,null]},-1],["cr:12495",[],{"__rc":[null,null]},-1],["cr:665",[],{"__rc":[null,null]},-1],["cr:4489",[],{"__rc":[null,null]},-1],["cr:6218",[],{"__rc":[null,"Aa7ae4-Pf8N1Csir59TuxWhT6B-apGTbURYn14T-3PE87qW_5WIhZSW9D_e10gT9BqEUclhE4UDb1Kxgsp-ATgz5cIpoewBrqwx990hngSIBRC_8arB2eRBgzA"]},-1],["cr:7000",[],{"__rc":[null,"Aa4qZs_57g4L3ic19DSyorNmLKY_MWH3fDXoPm6HXVJAbSrEFak0oVu6IoA_smgDcdTRZKmpeapuLdWx_a90moqH2uOQITamt6YhbzYtQt5pUPbSDooLOjEyCQ"]},-1],["cr:7351",[],{"__rc":[null,null]},-1],["cr:8915",[],{"__rc":[null,null]},-1],["cr:10099",[],{"__rc":[null,null]},-1],["cr:10200",["MWLSSchemaEphemeral"],{"__rc":["MWLSSchemaEphemeral",null]},-1],["cr:10755",[],{"__rc":[null,null]},-1],["cr:8713",["HelpCenterLocalePopoverQuery.facebook.graphql"],{"__rc":["HelpCenterLocalePopoverQuery.facebook.graphql",null]},-1],["cr:720",["ResumableUploadServiceBlue"],{"__rc":["ResumableUploadSer | 2026-01-13T08:48:25 |
https://developer.mozilla.org/en-US/docs/Web/HTML/Guides/Date_and_time_formats | Using date and time formats in HTML - HTML | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTML Guides Date and time formats Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 한국어 中文 (简体) Using date and time formats in HTML Certain HTML elements use date and/or time values. The formats of the strings that specify these values are described in this article. Elements that use such formats include certain forms of the <input> element that let the user choose or specify a date, time, or both, as well as the <ins> and <del> elements, whose datetime attribute specifies the date or date and time at which the insertion or deletion of content occurred. For <input> , the type values of inputs whose value contains a string representing a date and/or time are: date datetime-local month time week In this article Examples Basics Week strings Month strings Date strings Time strings Local date and time strings Global date and time strings Date issues See also Examples Before getting into the intricacies of how date and time strings are written and parsed in HTML, here are some examples that should give you a good idea what the more commonly-used date and time string formats look like. Example HTML date and time strings String Date and/or time 2005-06-07 June 7, 2005 [details] 08:45 8:45 AM [details] 08:45:25 8:45 AM and 25 seconds [details] 0033-08-04T03:40 3:40 AM on August 4, 33 [details] 1977-04-01T14:00:30 30 seconds after 2:00 PM on April 1, 1977 [details] 1901-01-01T00:00Z Midnight UTC on January 1, 1901 [details] 1901-01-01T00:00:01-04:00 1 second past midnight Eastern Standard Time (EST) on January 1, 1901 [details] Basics Before looking at the various formats of date and time related strings used by HTML elements, it is helpful to understand a few fundamental facts about the way they're defined. HTML uses a variation of the ISO 8601 standard for its date and time strings. It's worth reviewing the descriptions of the formats you're using in order to ensure that your strings are in fact compatible with HTML, as the HTML specification includes algorithms for parsing these strings that is actually more precise than ISO 8601, so there can be subtle differences in how date and time strings are expected to look. Character set Dates and times in HTML are always strings which use the ASCII character set. Year numbers In order to simplify the basic format used for date strings in HTML, the specification requires that all years be given using the modern (or proleptic ) Gregorian calendar . While user interfaces may allow entry of dates using other calendars, the underlying value always uses the Gregorian calendar. While the Gregorian calendar wasn't created until the year 1582 (replacing the similar Julian calendar), for HTML's purposes, the Gregorian calendar is extended back to the year 1 C.E. Make sure any older dates account for this. For the purposes of HTML dates, years are always at least four digits long; years prior to the year 1000 are padded with leading zeroes ( 0 ), so the year 72 is written as 0072 . Years prior to the year 1 C.E. are not supported, so HTML doesn't support years 1 B.C.E. (1 B.C.) or earlier. A year is normally 365 days long, except during leap years . Leap years A leap year is any year which is divisible by 400 or the year is divisible by 4 but not by 100. Although the calendar year is normally 365 days long, it actually takes the planet Earth approximately 365.2422 days to complete a single orbit around the sun. Leap years help to adjust the calendar to keep it synchronized with the actual position of the planet in its orbit. Adding a day to the year every four years essentially makes the average year 365.25 days long, which is close to correct. The adjustments to the algorithm (taking a leap year when the year can be divided by 400, and skipping leap years when the year is divisible by 100) help to bring the average even closer to the correct number of days (365.2425 days). Scientists occasionally add leap seconds to the calendar (seriously) to handle the remaining three ten-thousandths of a day and to compensate for the gradual, naturally occurring slowing of Earth's rotation. While month 02 , February, normally has 28 days, it has 29 days in leap years. Months of the year There are 12 months in the year, numbered 1 through 12. They are always represented by a two-digit ASCII string whose value ranges from 01 through 12 . See the table in the section Days of the month for the month numbers and their corresponding names (and lengths in days). Days of the month Month numbers 1, 3, 5, 7, 8, 10, and 12 are 31 days long. Months 4, 6, 9, and 11 are 30 days long. Month 2, February, is 28 days long most years, but is 29 days long in leap years. This is detailed in the following table. The months of the year and their lengths in days Month number Name (English) Length in days 01 January 31 02 February 28 (29 in leap years) 03 March 31 04 April 30 05 May 31 06 June 30 07 July 31 08 August 31 09 September 30 10 October 31 11 November 30 12 December 31 Week strings A week string specifies a week within a particular year. A valid week string consists of a valid year number , followed by a hyphen character ( - , or U+002D), then the capital letter W (U+0057), followed by a two-digit week of the year value. The week of the year is a two-digit string between 01 and 53 . Each week begins on Monday and ends on Sunday. That means it's possible for the first few days of January to be considered part of the previous week-year, and for the last few days of December to be considered part of the following week-year. The first week of the year is the week that contains the first Thursday of the year . For example, the first Thursday of 1953 was on January 1, so that week—beginning on Monday, December 29—is considered the first week of the year. Therefore, December 30, 1952 occurs during the week 1953-W01 . A year has 53 weeks if: The first day of the calendar year (January 1) is a Thursday or The first day of the year (January 1) is a Wednesday and the year is a leap year All other years have 52 weeks. Week string Week and year (Date range) 2001-W37 Week 37, 2001 (September 10-16, 2001) 1953-W01 Week 1, 1953 (December 29, 1952-January 4, 1953) 1948-W53 Week 53, 1948 (December 27, 1948-January 2, 1949) 1949-W01 Week 1, 1949 (January 3-9, 1949) 0531-W16 Week 16, 531 (April 13-19, 531) 0042-W04 Week 4, 42 (January 21-27, 42) Note that both the year and week numbers are padded with leading zeroes, with the year padded to four digits and the week to two. Month strings A month string represents a specific month in time, rather than a generic month of the year. That is, rather than representing "January," an HTML month string represents a month and year paired, like "January 1972." A valid month string consists of a valid year number (a string of at least four digits), followed by a hyphen character ( - , or U+002D), followed by a two-digit numeric month number , where 01 represents January and 12 represents December. Month string Month and year 17310-09 September, 17310 2019-01 January, 2019 1993-11 November, 1993 0571-04 April, 571 0001-07 July, 1 C.E. Notice that all years are at least four characters long; years that are fewer than four digits long are padded with leading zeroes. Date strings A valid date string consists of a month string , followed by a hyphen character ( - , or U+002D), followed by a two-digit day of the month . Date string Full date 1993-11-01 November 1, 1993 1066-10-14 October 14, 1066 0571-04-22 April 22, 571 0062-02-05 February 5, 62 Time strings A time string can specify a time with precision to the minute, second, or to the millisecond. Specifying only the hour or minute isn't permitted. A valid time string minimally consists of a two-digit hour followed by a colon ( : , U+003A), then a two-digit minute. The minute may optionally be followed by another colon and a two-digit number of seconds. Milliseconds may be specified, optionally, by adding a decimal point character ( . , U+002E) followed by one, two, or three digits. There are some additional basic rules: The hour is always specified using the 24-hour clock, with 00 being midnight and 11 PM being 23 . No values outside the range 00 – 23 are permitted. The minute must be a two-digit number between 00 and 59 . No values outside that range are allowed. If the number of seconds is omitted (to specify a time accurate only to the minute), no colon should follow the number of minutes. If specified, the integer portion of the number of seconds must be between 00 and 59 . You cannot specify leap seconds by using values like 60 or 61 . If the number of seconds is specified and is an integer, it must not be followed by a decimal point. If a fraction of a second is included, it may be from one to three digits long, indicating the number of milliseconds. It follows the decimal point placed after the seconds component of the time string. Time string Time 00:00:30.75 12:00:30.75 AM (30.75 seconds after midnight) 12:15 12:15 PM 13:44:25 1:44:25 PM (25 seconds after 1:44 PM) Local date and time strings A valid datetime-local string consists of a date string and a time string concatenated together with either the letter T or a space character separating them. No information about the time zone is included in the string; the date and time is presumed to be in the user's local time zone. When you set the value of a datetime-local input, the string is normalized into a standard form. Normalized datetime strings always use the letter T to separate the date and the time, and the time portion of the string is as short as possible. This is done by leaving out the seconds component if its value is :00 . Examples of valid datetime-local strings Date/time string Normalized date/time string Actual date and time 1986-01-28T11:38:00.01 1986-01-28T11:38:00.01 January 28, 1986 at 11:38:00.01 AM 1986-01-28 11:38:00.010 1986-01-28T11:38:00.01 Note that after normalization, this is the same string as the previous datetime-local string. The space has been replaced with the T character and the trailing zero in the fraction of a second has been removed to make the string as short as possible. January 28, 1986 at 11:38:00.01 AM 0170-07-31T22:00:00 0170-07-31T22:00 Note that the normalized form of this date drops the :00 indicating the number of seconds to be zero, because the seconds are optional when zero, and the normalized string minimizes the length of the string. July 31, 170 at 10:00 PM Global date and time strings A global date and time string specifies a date and time as well as the time zone in which it occurs. A valid global date and time string is the same format as a local date and time string , except it has a time zone string appended to the end, following the time. Time zone offset string A time zone offset string specifies the offset in either a positive or a negative number of hours and minutes from the standard time base. There are two standard time bases, which are very close to the same, but not exactly the same: For dates after the establishment of Coordinated Universal Time (UTC) in the early 1960s, the time base is Z and the offset indicates a particular time zone's offset from the time at the prime meridian at 0º longitude (which passes through the Royal Observatory at Greenwich, England). For dates prior to UTC, the time base is instead expressed in terms of UT1 , which is the contemporary Earth solar time at the prime meridian. The time zone string is appended immediately following the time in the date and time string. You can specify Z as the time zone offset string to indicate that the time is specified in UTC. Otherwise, the time zone string is constructed as follows: A character indicating the sign of the offset: the plus character ( + , or U+002B) for time zones to the east of the prime meridian or the minus character ( - , or U+002D) for time zones to the west of the prime meridian. A two-digit number of hours that the time zone is offset from the prime meridian. This value must be between 00 and 23 . An optional colon ( : ) character. A two-digit number of minutes past the hour; this value must be between 00 and 59 . While this format allows for time zones between -23:59 and +23:59, the current range of time zone offsets is -12:00 to +14:00, and no time zones are currently offset from the hour by anything other than 00 , 30 , or 45 minutes. This may change at more or less anytime, since countries are free to tamper with their time zones at any time and in any way they wish to do so. Examples of valid global date and time strings Global date and time string Actual global date and time Date and time at prime meridian 2005-06-07T00:00Z June 7, 2005 at midnight UTC June 7, 2005 at midnight 1789-08-22T12:30:00.1-04:00 August 22, 1789 at a tenth of a second past 12:30 PM Eastern Daylight Time (EDT) August 22, 1789 at a tenth of a second past 4:30 PM 3755-01-01 00:00+10:00 January 1, 3755 at midnight Australian Eastern Standard Time (AEST) December 31, 3754 at 2:00 PM Date issues Because of data storage and precision issues, you may want to be aware of a few client-side and server-side issues. The Y2K38 Problem (often server-side) JavaScript uses double precision floating points to store dates, as with all numbers, meaning that JavaScript code will not suffer from the Y2K38 problem unless integer coercion/bit-hacks are used because all JavaScript bit operators use 32-bit signed 2s-complement integers. The problem is with the server side of things: storage of dates greater than 2^31 - 1. To fix this problem, you must store all dates using either unsigned 32-bit integers, signed 64-bit integers, or double-precision floating points on the server. If your server is written in PHP, the fix may require upgrading your PHP to a more recent version, and upgrading your hardware to x86_64 or IA64. If you are stuck with other hardware, you can try to emulate 64-bit hardware inside a 32-bit virtual machine, but most VMs don't support this kind of virtualization, since stability may suffer, and performance will definitely suffer greatly. The Y10k Problem (often client-side) In many servers, dates are stored as numbers instead of as strings--numbers of a fixed size and agnostic of format (aside from endianness). After the year 10,000, those numbers will just be a bit bigger than before, so many servers will not see issues with forms submitted after the year 10,000. The problem is with the client side of things: parsing of dates with more than 4 digits in the year. html <!--midnight of January 1st, 10000: the exact time of Y10K--> <input type="datetime-local" value="+010000-01-01T05:00" /> We need to prepare our code for any number of digits — not just 5. The following JavaScript function programmatically sets the value: js function setValue(element, date) { const isoString = date.toISOString(); element.value = isoString.substring(0, isoString.indexOf("T") + 6); } Why worry about the Y10K problem if it is going to happen many centuries after your death? Exactly because you will already be dead, so the companies using your software will be stuck using your software without any other coder who knows the system well enough to come in and fix it. See also <input> <ins> and <del> : see the datetime attribute, which specifies either a date or a local date and time at which the content was inserted or deleted The ISO 8601 specification Representing dates & times in the JavaScript Guide The JavaScript Date object The Intl.DateTimeFormat object for formatting dates and times for a given locale Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jul 9, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTML Guides Cheatsheet Comments Constraint validation Content categories Date and time formats Microdata Microformats Quirks and standards modes Responsive images How to Define terms with HTML Use data attributes Use cross-origin images Add a hitmap on top of an image Author fast-loading HTML pages Add JavaScript Reference Elements <a> <abbr> <acronym> Deprecated <address> <area> <article> <aside> <audio> <b> <base> <bdi> <bdo> <big> Deprecated <blockquote> <body> <br> <button> <canvas> <caption> <center> Deprecated <cite> <code> <col> <colgroup> <data> <datalist> <dd> <del> <details> <dfn> <dialog> <dir> Deprecated <div> <dl> <dt> <em> <embed> <fencedframe> Experimental <fieldset> <figcaption> <figure> <font> Deprecated <footer> <form> <frame> Deprecated <frameset> Deprecated <h1> <head> <header> <hgroup> <hr> <html> <i> <iframe> <img> <input> <ins> <kbd> <label> <legend> <li> <link> <main> <map> <mark> <marquee> Deprecated <menu> <meta> <meter> <nav> <nobr> Deprecated <noembed> Deprecated <noframes> Deprecated <noscript> <object> <ol> <optgroup> <option> <output> <p> <param> Deprecated <picture> <plaintext> Deprecated <pre> <progress> <q> <rb> Deprecated <rp> <rt> <rtc> Deprecated <ruby> <s> <samp> <script> <search> <section> <select> <selectedcontent> Experimental <slot> <small> <source> <span> <strike> Deprecated <strong> <style> <sub> <summary> <sup> <table> <tbody> <td> <template> <textarea> <tfoot> <th> <thead> <time> <title> <tr> <track> <tt> Deprecated <u> <ul> <var> <video> <wbr> <xmp> Deprecated Attributes accept autocomplete capture content crossorigin dirname disabled elementtiming fetchpriority for form max maxlength min minlength multiple pattern placeholder readonly rel required size step Global attributes accesskey anchor Experimental Non-standard autocapitalize autocorrect autofocus class contenteditable data-* dir draggable enterkeyhint exportparts hidden id inert inputmode is itemid itemprop itemref itemscope itemtype lang nonce part popover slot spellcheck style tabindex title translate virtualkeyboardpolicy Experimental writingsuggestions Attributes by element <input> type <input type="button"> <input type="checkbox"> <input type="color"> <input type="date"> <input type="datetime-local"> <input type="email"> <input type="file"> <input type="hidden"> <input type="image"> <input type="month"> <input type="number"> <input type="password"> <input type="radio"> <input type="range"> <input type="reset"> <input type="search"> <input type="submit"> <input type="tel"> <input type="text"> <input type="time"> <input type="url"> <input type="week"> <script> type importmap speculationrules Experimental <meta> name color-scheme referrer robots theme-color viewport <meta> http-equiv Attribute values rel keywords rel="alternate stylesheet" rel="compression-dictionary" Experimental rel="dns-prefetch" rel="manifest" rel="me" rel="modulepreload" rel="noopener" rel="noreferrer" rel="preconnect" rel="prefetch" rel="preload" rel="prerender" Non-standard Deprecated Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements | HTML elements reference - HTML | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTML Reference Elements Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) HTML elements reference This page lists all the HTML elements , which are created using tags . They are grouped by function to help you find what you have in mind easily. An alphabetical list of all elements is provided in the sidebar on every element's page as well as this one. Note: For more information about the basics of HTML elements and attributes, see Anatomy of an HTML element . In this article Main root Document metadata Sectioning root Content sectioning Text content Inline text semantics Image and multimedia Embedded content SVG and MathML Scripting Demarcating edits Table content Forms Interactive elements Web Components Obsolete and deprecated elements See also Main root Element Description <html> Represents the root (top-level element) of an HTML document, so it is also referred to as the root element . All other elements must be descendants of this element. Document metadata Metadata contains information about the page. This includes information about styles, scripts and data to help software ( search engines , browsers , etc.) use and render the page. Metadata for styles and scripts may be defined in the page or linked to another file that has the information. Element Description <base> Specifies the base URL to use for all relative URLs in a document. There can be only one such element in a document. <head> Contains machine-readable information (metadata) about the document, like its title , scripts , and style sheets . <link> Specifies relationships between the current document and an external resource. This element is most commonly used to link to CSS but is also used to establish site icons (both "favicon" style icons and icons for the home screen and apps on mobile devices) among other things. <meta> Represents metadata that cannot be represented by other HTML meta-related elements, like <base> , <link> , <script> , <style> and <title> . <style> Contains style information for a document or part of a document. It contains CSS, which is applied to the contents of the document containing this element. <title> Defines the document's title that is shown in a browser 's title bar or a page's tab. It only contains text; HTML tags within the element, if any, are also treated as plain text. Sectioning root Element Description <body> Represents the content of an HTML document. There can be only one such element in a document. Content sectioning Content sectioning elements allow you to organize the document content into logical pieces. Use the sectioning elements to create a broad outline for your page content, including header and footer navigation, and heading elements to identify sections of content. Element Description <address> Indicates that the enclosed HTML provides contact information for a person or people, or for an organization. <article> Represents a self-contained composition in a document, page, application, or site, which is intended to be independently distributable or reusable (e.g., in syndication). Examples include a forum post, a magazine or newspaper article, a blog entry, a product card, a user-submitted comment, an interactive widget or gadget, or any other independent item of content. <aside> Represents a portion of a document whose content is only indirectly related to the document's main content. Asides are frequently presented as sidebars or call-out boxes. <footer> Represents a footer for its nearest ancestor sectioning content or sectioning root element. A <footer> typically contains information about the author of the section, copyright data, or links to related documents. <header> Represents introductory content, typically a group of introductory or navigational aids. It may contain some heading elements but also a logo, a search form, an author name, and other elements. <h1> , <h2> , <h3> , <h4> , <h5> , <h6> Represent six levels of section headings. <h1> is the highest section level and <h6> is the lowest. <hgroup> Represents a heading grouped with any secondary content, such as subheadings, an alternative title, or a tagline. <main> Represents the dominant content of the body of a document. The main content area consists of content that is directly related to or expands upon the central topic of a document, or the central functionality of an application. <nav> Represents a section of a page whose purpose is to provide navigation links, either within the current document or to other documents. Common examples of navigation sections are menus, tables of contents, and indexes. <section> Represents a generic standalone section of a document, which doesn't have a more specific semantic element to represent it. Sections should always have a heading, with very few exceptions. <search> Represents a part that contains a set of form controls or other content related to performing a search or filtering operation. Text content Use HTML text content elements to organize blocks or sections of content placed between the opening <body> and closing </body> tags. Important for accessibility and SEO , these elements identify the purpose or structure of that content. Element Description <blockquote> Indicates that the enclosed text is an extended quotation. Usually, this is rendered visually by indentation. A URL for the source of the quotation may be given using the cite attribute, while a text representation of the source can be given using the <cite> element. <dd> Provides the description, definition, or value for the preceding term ( <dt> ) in a description list ( <dl> ). <div> The generic container for flow content. It has no effect on the content or layout until styled in some way using CSS (e.g., styling is directly applied to it, or some kind of layout model like flexbox is applied to its parent element). <dl> Represents a description list. The element encloses a list of groups of terms (specified using the <dt> element) and descriptions (provided by <dd> elements). Common uses for this element are to implement a glossary or to display metadata (a list of key-value pairs). <dt> Specifies a term in a description or definition list, and as such must be used inside a <dl> element. It is usually followed by a <dd> element; however, multiple <dt> elements in a row indicate several terms that are all defined by the immediate next <dd> element. <figcaption> Represents a caption or legend describing the rest of the contents of its parent <figure> element. <figure> Represents self-contained content, potentially with an optional caption, which is specified using the <figcaption> element. The figure, its caption, and its contents are referenced as a single unit. <hr> Represents a thematic break between paragraph-level elements: for example, a change of scene in a story, or a shift of topic within a section. <li> Represents an item in a list. It must be contained in a parent element: an ordered list ( <ol> ), an unordered list ( <ul> ), or a menu ( <menu> ). In menus and unordered lists, list items are usually displayed using bullet points. In ordered lists, they are usually displayed with an ascending counter on the left, such as a number or letter. <menu> A semantic alternative to <ul> , but treated by browsers (and exposed through the accessibility tree) as no different than <ul> . It represents an unordered list of items (which are represented by <li> elements). <ol> Represents an ordered list of items — typically rendered as a numbered list. <p> Represents a paragraph. Paragraphs are usually represented in visual media as blocks of text separated from adjacent blocks by blank lines and/or first-line indentation, but HTML paragraphs can be any structural grouping of related content, such as images or form fields. <pre> Represents preformatted text which is to be presented exactly as written in the HTML file. The text is typically rendered using a non-proportional, or monospaced , font. Whitespace inside this element is displayed as written. <ul> Represents an unordered list of items, typically rendered as a bulleted list. Inline text semantics Use the HTML inline text semantic to define the meaning, structure, or style of a word, line, or any arbitrary piece of text. Element Description <a> Together with its href attribute, creates a hyperlink to web pages, files, email addresses, locations within the current page, or anything else a URL can address. <abbr> Represents an abbreviation or acronym. <b> Used to draw the reader's attention to the element's contents, which are not otherwise granted special importance. This was formerly known as the Boldface element, and most browsers still draw the text in boldface. However, you should not use <b> for styling text or granting importance. If you wish to create boldface text, you should use the CSS font-weight property. If you wish to indicate an element is of special importance, you should use the <strong> element. <bdi> Tells the browser's bidirectional algorithm to treat the text it contains in isolation from its surrounding text. It's particularly useful when a website dynamically inserts some text and doesn't know the directionality of the text being inserted. <bdo> Overrides the current directionality of text, so that the text within is rendered in a different direction. <br> Produces a line break in text (carriage-return). It is useful for writing a poem or an address, where the division of lines is significant. <cite> Used to mark up the title of a creative work. The reference may be in an abbreviated form according to context-appropriate conventions related to citation metadata. <code> Displays its contents styled in a fashion intended to indicate that the text is a short fragment of computer code. By default, the content text is displayed using the user agent's default monospace font. <data> Links a given piece of content with a machine-readable translation. If the content is time- or date-related, the <time> element must be used. <dfn> Used to indicate the term being defined within the context of a definition phrase or sentence. The ancestor <p> element, the <dt> / <dd> pairing, or the nearest section ancestor of the <dfn> element, is considered to be the definition of the term. <em> Marks text that has stress emphasis. The <em> element can be nested, with each nesting level indicating a greater degree of emphasis. <i> Represents a range of text that is set off from the normal text for some reason, such as idiomatic text, technical terms, and taxonomical designations, among others. Historically, these have been presented using italicized type, which is the original source of the <i> naming of this element. <kbd> Represents a span of inline text denoting textual user input from a keyboard, voice input, or any other text entry device. By convention, the user agent defaults to rendering the contents of a <kbd> element using its default monospace font, although this is not mandated by the HTML standard. <mark> Represents text which is marked or highlighted for reference or notation purposes due to the marked passage's relevance in the enclosing context. <q> Indicates that the enclosed text is a short inline quotation. Most modern browsers implement this by surrounding the text in quotation marks. This element is intended for short quotations that don't require paragraph breaks; for long quotations use the <blockquote> element. <rp> Used to provide fall-back parentheses for browsers that do not support the display of ruby annotations using the <ruby> element. One <rp> element should enclose each of the opening and closing parentheses that wrap the <rt> element that contains the annotation's text. <rt> Specifies the ruby text component of a ruby annotation, which is used to provide pronunciation, translation, or transliteration information for East Asian typography. The <rt> element must always be contained within a <ruby> element. <ruby> Represents small annotations that are rendered above, below, or next to base text, usually used for showing the pronunciation of East Asian characters. It can also be used for annotating other kinds of text, but this usage is less common. <s> Renders text with a strikethrough, or a line through it. Use the <s> element to represent things that are no longer relevant or no longer accurate. However, <s> is not appropriate when indicating document edits; for that, use the <del> and <ins> elements, as appropriate. <samp> Used to enclose inline text which represents sample (or quoted) output from a computer program. Its contents are typically rendered using the browser's default monospaced font (such as Courier or Lucida Console). <small> Represents side-comments and small print, like copyright and legal text, independent of its styled presentation. By default, it renders text within it one font size smaller, such as from small to x-small . <span> A generic inline container for phrasing content, which does not inherently represent anything. It can be used to group elements for styling purposes (using the class or id attributes), or because they share attribute values, such as lang . It should be used only when no other semantic element is appropriate. <span> is very much like a div element, but div is a block-level element whereas a <span> is an inline-level element . <strong> Indicates that its contents have strong importance, seriousness, or urgency. Browsers typically render the contents in bold type. <sub> Specifies inline text which should be displayed as subscript for solely typographical reasons. Subscripts are typically rendered with a lowered baseline using smaller text. <sup> Specifies inline text which is to be displayed as superscript for solely typographical reasons. Superscripts are usually rendered with a raised baseline using smaller text. <time> Represents a specific period in time. It may include the datetime attribute to translate dates into machine-readable format, allowing for better search engine results or custom features such as reminders. <u> Represents a span of inline text which should be rendered in a way that indicates that it has a non-textual annotation. This is rendered by default as a single solid underline but may be altered using CSS. <var> Represents the name of a variable in a mathematical expression or a programming context. It's typically presented using an italicized version of the current typeface, although that behavior is browser-dependent. <wbr> Represents a word break opportunity—a position within text where the browser may optionally break a line, though its line-breaking rules would not otherwise create a break at that location. Image and multimedia HTML supports various multimedia resources such as images, audio, and video. Element Description <area> Defines an area inside an image map that has predefined clickable areas. An image map allows geometric areas on an image to be associated with hyperlink . <audio> Used to embed sound content in documents. It may contain one or more audio sources, represented using the src attribute or the source element: the browser will choose the most suitable one. It can also be the destination for streamed media, using a MediaStream . <img> Embeds an image into the document. <map> Used with <area> elements to define an image map (a clickable link area). <track> Used as a child of the media elements, audio and video. It lets you specify timed text tracks (or time-based data), for example to automatically handle subtitles. The tracks are formatted in WebVTT format ( .vtt files)—Web Video Text Tracks. <video> Embeds a media player which supports video playback into the document. You can also use <video> for audio content, but the audio element may provide a more appropriate user experience. Embedded content In addition to regular multimedia content, HTML can include a variety of other content, even if it's not always easy to interact with. Element Description <embed> Embeds external content at the specified point in the document. This content is provided by an external application or other source of interactive content such as a browser plug-in. <fencedframe> Represents a nested browsing context, like <iframe> but with more native privacy features built in. <iframe> Represents a nested browsing context, embedding another HTML page into the current one. <object> Represents an external resource, which can be treated as an image, a nested browsing context, or a resource to be handled by a plugin. <picture> Contains zero or more <source> elements and one <img> element to offer alternative versions of an image for different display/device scenarios. <source> Specifies multiple media resources for the picture, the audio element, or the video element. It is a void element, meaning that it has no content and does not have a closing tag. It is commonly used to offer the same media content in multiple file formats in order to provide compatibility with a broad range of browsers given their differing support for image file formats and media file formats . SVG and MathML You can embed SVG and MathML content directly into HTML documents, using the <svg> and "> <math> elements. Element Description <svg> Container defining a new coordinate system and viewport . It is used as the outermost element of SVG documents, but it can also be used to embed an SVG fragment inside an SVG or HTML document. "> <math> The top-level element in MathML. Every valid MathML instance must be wrapped in it. In addition, you must not nest a second <math> element in another, but you can have an arbitrary number of other child elements in it. Scripting To create dynamic content and Web applications, HTML supports the use of scripting languages, most prominently JavaScript. Certain elements support this capability. Element Description <canvas> Container element to use with either the canvas scripting API or the WebGL API to draw graphics and animations. <noscript> Defines a section of HTML to be inserted if a script type on the page is unsupported or if scripting is currently turned off in the browser. <script> Used to embed executable code or data; this is typically used to embed or refer to JavaScript code. The <script> element can also be used with other languages, such as WebGL 's GLSL shader programming language and JSON . Demarcating edits These elements let you provide indications that specific parts of the text have been altered. Element Description <del> Represents a range of text that has been deleted from a document. This can be used when rendering "track changes" or source code diff information, for example. The <ins> element can be used for the opposite purpose: to indicate text that has been added to the document. <ins> Represents a range of text that has been added to a document. You can use the <del> element to similarly represent a range of text that has been deleted from the document. Table content The elements here are used to create and handle tabular data. Element Description <caption> Specifies the caption (or title) of a table. <col> Defines one or more columns in a column group represented by its implicit or explicit parent <colgroup> element. The <col> element is only valid as a child of a <colgroup> element that has no span attribute defined. <colgroup> Defines a group of columns within a table. <table> Represents tabular data—that is, information presented in a two-dimensional table comprised of rows and columns of cells containing data. <tbody> Encapsulates a set of table rows ( <tr> elements), indicating that they comprise the body of a table's (main) data. <td> A child of the <tr> element, it defines a cell of a table that contains data. <tfoot> Encapsulates a set of table rows ( <tr> elements), indicating that they comprise the foot of a table with information about the table's columns. This is usually a summary of the columns, e.g., a sum of the given numbers in a column. <th> A child of the <tr> element, it defines a cell as the header of a group of table cells. The nature of this group can be explicitly defined by the scope and headers attributes. <thead> Encapsulates a set of table rows ( <tr> elements), indicating that they comprise the head of a table with information about the table's columns. This is usually in the form of column headers ( <th> elements). <tr> Defines a row of cells in a table. The row's cells can then be established using a mix of <td> (data cell) and <th> (header cell) elements. Forms HTML provides several elements that can be used together to create forms that the user can fill out and submit to the website or application. Further information about this available in the HTML forms guide . Element Description <button> An interactive element activated by a user with a mouse, keyboard, finger, voice command, or other assistive technology. Once activated, it performs an action, such as submitting a form or opening a dialog. <datalist> Contains a set of <option> elements that represent the permissible or recommended options available to choose from within other controls. <fieldset> Used to group several controls as well as labels ( <label> ) within a web form. <form> Represents a document section containing interactive controls for submitting information. <input> Used to create interactive controls for web-based forms to accept data from the user; a wide variety of types of input data and control widgets are available, depending on the device and user agent. The <input> element is one of the most powerful and complex in all of HTML due to the sheer number of combinations of input types and attributes. <label> Represents a caption for an item in a user interface. <legend> Represents a caption for the content of its parent <fieldset> . <meter> Represents either a scalar value within a known range or a fractional value. <optgroup> Creates a grouping of options within a <select> element. <option> Used to define an item contained in a <select> , an <optgroup> , or a <datalist> element. As such, <option> can represent menu items in popups and other lists of items in an HTML document. <output> Container element into which a site or app can inject the results of a calculation or the outcome of a user action. <progress> Displays an indicator showing the completion progress of a task, typically displayed as a progress bar. <select> Represents a control that provides a menu of options. <selectedcontent> Displays the content of the currently selected <option> inside a closed <select> element. <textarea> Represents a multi-line plain-text editing control, useful when you want to allow users to enter a sizeable amount of free-form text, for example, a comment on a review or feedback form. Interactive elements HTML offers a selection of elements that help to create interactive user interface objects. Element Description <details> Creates a disclosure widget in which information is visible only when the widget is toggled into an "open" state. A summary or label must be provided using the <summary> element. <dialog> Represents a dialog box or other interactive component, such as a dismissible alert, inspector, or subwindow. <summary> Specifies a summary, caption, or legend for a details element's disclosure box. Clicking the <summary> element toggles the state of the parent <details> element open and closed. Web Components Web Components is an HTML-related technology that makes it possible to, essentially, create and use custom elements as if it were regular HTML. In addition, you can create custom versions of standard HTML elements. Element Description <slot> Part of the Web Components technology suite, this element is a placeholder inside a web component that you can fill with your own markup, which lets you create separate DOM trees and present them together. <template> A mechanism for holding HTML that is not to be rendered immediately when a page is loaded but may be instantiated subsequently during runtime using JavaScript. Obsolete and deprecated elements Warning: These are old HTML elements that are deprecated and should not be used. You should never use them in new projects, and you should replace them in old projects as soon as you can. They are listed here for completeness only. Element Description <acronym> Allows authors to clearly indicate a sequence of characters that compose an acronym or abbreviation for a word. <big> Renders the enclosed text at a font size one level larger than the surrounding text ( medium becomes large , for example). The size is capped at the browser's maximum permitted font size. <center> Displays its block-level or inline contents centered horizontally within its containing element. <content> An obsolete part of the Web Components suite of technologies—was used inside of Shadow DOM as an insertion point, and wasn't meant to be used in ordinary HTML. It has now been replaced by the <slot> element, which creates a point in the DOM at which a shadow DOM can be inserted. Consider using <slot> instead. <dir> Container for a directory of files and/or folders, potentially with styles and icons applied by the user agent. Do not use this obsolete element; instead, you should use the <ul> element for lists, including lists of files. <font> Defines the font size, color and face for its content. <frame> Defines a particular area in which another HTML document can be displayed. A frame should be used within a <frameset> . <frameset> Used to contain <frame> elements. <image> An ancient and poorly supported precursor to the <img> element. It should not be used. <marquee> Used to insert a scrolling area of text. You can control what happens when the text reaches the edges of its content area using its attributes. <menuitem> Represents a command that a user is able to invoke through a popup menu. This includes context menus, as well as menus that might be attached to a menu button. <nobr> Prevents the text it contains from automatically wrapping across multiple lines, potentially resulting in the user having to scroll horizontally to see the entire width of the text. <noembed> An obsolete, non-standard way to provide alternative, or "fallback", content for browsers that do not support the embed element or do not support the type of embedded content an author wishes to use. This element was deprecated in HTML 4.01 and above in favor of placing fallback content between the opening and closing tags of an <object> element. <noframes> Provides content to be presented in browsers that don't support (or have disabled support for) the <frame> element. Although most commonly-used browsers support frames, there are exceptions, including certain special-use browsers including some mobile browsers, as well as text-mode browsers. <param> Defines parameters for an <object> element. <plaintext> Renders everything following the start tag as raw text, ignoring any following HTML. There is no closing tag, since everything after it is considered raw text. <rb> Used to delimit the base text component of a ruby annotation, i.e., the text that is being annotated. One <rb> element should wrap each separate atomic segment of the base text. <rtc> Embraces semantic annotations of characters presented in a ruby of <rb> elements used inside of <ruby> element. <rb> elements can have both pronunciation ( <rt> ) and semantic ( <rtc> ) annotations. <shadow> An obsolete part of the Web Components technology suite that was intended to be used as a shadow DOM insertion point. You might have used it if you have created multiple shadow roots under a shadow host. Consider using <slot> instead. <strike> Places a strikethrough (horizontal line) over text. <tt> Creates inline text which is presented using the user agent default monospace font face. This element was created for the purpose of rendering text as it would be displayed on a fixed-width display such as a teletype, text-only screen, or line printer. <xmp> Renders text between the start and end tags without interpreting the HTML in between and using a monospaced font. The HTML2 specification recommended that it should be rendered wide enough to allow 80 characters per line. See also Element interface Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 9, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTML Guides Cheatsheet Comments Constraint validation Content categories Date and time formats Microdata Microformats Quirks and standards modes Responsive images How to Define terms with HTML Use data attributes Use cross-origin images Add a hitmap on top of an image Author fast-loading HTML pages Add JavaScript Reference Elements <a> <abbr> <acronym> Deprecated <address> <area> <article> <aside> <audio> <b> <base> <bdi> <bdo> <big> Deprecated <blockquote> <body> <br> <button> <canvas> <caption> <center> Deprecated <cite> <code> <col> <colgroup> <data> <datalist> <dd> <del> <details> <dfn> <dialog> <dir> Deprecated <div> <dl> <dt> <em> <embed> <fencedframe> Experimental <fieldset> <figcaption> <figure> <font> Deprecated <footer> <form> <frame> Deprecated <frameset> Deprecated <h1> <head> <header> <hgroup> <hr> <html> <i> <iframe> <img> <input> <ins> <kbd> <label> <legend> <li> <link> <main> <map> <mark> <marquee> Deprecated <menu> <meta> <meter> <nav> <nobr> Deprecated <noembed> Deprecated <noframes> Deprecated <noscript> <object> <ol> <optgroup> <option> <output> <p> <param> Deprecated <picture> <plaintext> Deprecated <pre> <progress> <q> <rb> Deprecated <rp> <rt> <rtc> Deprecated <ruby> <s> <samp> <script> <search> <section> <select> <selectedcontent> Experimental <slot> <small> <source> <span> <strike> Deprecated <strong> <style> <sub> <summary> <sup> <table> <tbody> <td> <template> <textarea> <tfoot> <th> <thead> <time> <title> <tr> <track> <tt> Deprecated <u> <ul> <var> <video> <wbr> <xmp> Deprecated Attributes accept autocomplete capture content crossorigin dirname disabled elementtiming fetchpriority for form max maxlength min minlength multiple pattern placeholder readonly rel required size step Global attributes accesskey anchor Experimental Non-standard autocapitalize autocorrect autofocus class contenteditable data-* dir draggable enterkeyhint exportparts hidden id inert inputmode is itemid itemprop itemref itemscope itemtype lang nonce part popover slot spellcheck style tabindex title translate virtualkeyboardpolicy Experimental writingsuggestions Attributes by element <input> type <input type="button"> <input type="checkbox"> <input type="color"> <input type="date"> <input type="datetime-local"> <input type="email"> <input type="file"> <input type="hidden"> <input type="image"> <input type="month"> <input type="number"> <input type="password"> <input type="radio"> <input type="range"> <input type="reset"> <input type="search"> <input type="submit"> <input type="tel"> <input type="text"> <input type="time"> <input type="url"> <input type="week"> <script> type importmap speculationrules Experimental <meta> name color-scheme referrer robots theme-color viewport <meta> http-equiv Attribute values rel keywords rel="alternate stylesheet" rel="compression-dictionary" Experimental rel="dns-prefetch" rel="manifest" rel="me" rel="modulepreload" rel="noopener" rel="noreferrer" rel="preconnect" rel="prefetch" rel="preload" rel="prerender" Non-standard Deprecated Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers | Using Web Workers - Web APIs | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Web APIs Web Workers API Using Web Workers Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 Русский 中文 (简体) 正體中文 (繁體) Using Web Workers Web Workers are a simple means for web content to run scripts in background threads. The worker thread can perform tasks without interfering with the user interface. In addition, they can make network requests using the fetch() or XMLHttpRequest APIs. Once created, a worker can send messages to the JavaScript code that created it by posting messages to an event handler specified by that code (and vice versa). This article provides a detailed introduction to using web workers. In this article Web Workers API Dedicated workers Shared workers About thread safety Content security policy Transferring data to and from workers: further details Embedded workers Further examples Other types of workers Debugging worker threads Functions and interfaces available in workers Specifications See also Web Workers API A worker is an object created using a constructor (e.g., Worker() ) that runs a named JavaScript file — this file contains the code that will run in the worker thread; workers run in another global context that is different from the current window . Thus, using the window shortcut to get the current global scope (instead of self ) within a Worker will return an error. The worker context is represented by a DedicatedWorkerGlobalScope object in the case of dedicated workers (standard workers that are utilized by a single script; shared workers use SharedWorkerGlobalScope ). A dedicated worker is only accessible from the script that first spawned it, whereas shared workers can be accessed from multiple scripts. Note: See The Web Workers API landing page for reference documentation on workers and additional guides. You can run whatever code you like inside the worker thread, with some exceptions. For example, you can't directly manipulate the DOM from inside a worker, or use some default methods and properties of the window object. But you can use a large number of items available under window , including WebSockets , and data storage mechanisms like IndexedDB . See Functions and classes available to workers for more details. Data is sent between workers and the main thread via a system of messages — both sides send their messages using the postMessage() method, and respond to messages via the onmessage event handler (the message is contained within the message event's data attribute). The data is copied rather than shared. Workers may in turn spawn new workers, as long as those workers are hosted within the same origin as the parent page. In addition, workers can make network requests using the fetch() or XMLHttpRequest APIs (although note that the responseXML attribute of XMLHttpRequest will always be null ). Dedicated workers As mentioned above, a dedicated worker is only accessible by the script that called it. In this section we'll discuss the JavaScript found in our Basic dedicated worker example ( run dedicated worker ): This allows you to enter two numbers to be multiplied together. The numbers are sent to a dedicated worker, multiplied together, and the result is returned to the page and displayed. This example is rather trivial, but we decided to keep it simple while introducing you to basic worker concepts. More advanced details are covered later on in the article. Worker feature detection For slightly more controlled error handling and backwards compatibility, it is a good idea to wrap your worker accessing code in the following ( main.js ): js if (window.Worker) { // … } Spawning a dedicated worker Creating a new worker is simple. All you need to do is call the Worker() constructor, specifying the URI of a script to execute in the worker thread ( main.js ): js const myWorker = new Worker("worker.js"); Note: Bundlers, including webpack , Vite , and Parcel , recommend passing URLs that are resolved relative to import.meta.url to the Worker() constructor. For example: js const myWorker = new Worker(new URL("worker.js", import.meta.url)); This way, the path is relative to the current script instead of the current HTML page, which allows the bundler to safely do optimizations like renaming (because otherwise the worker.js URL may point to a file not controlled by the bundler, so it cannot make any assumptions). Sending messages to and from a dedicated worker The magic of workers happens via the postMessage() method and the onmessage event handler. When you want to send a message to the worker, you post messages to it like this ( main.js ): js [first, second].forEach((input) => { input.onchange = () => { myWorker.postMessage([first.value, second.value]); console.log("Message posted to worker"); }; }); So here we have two <input> elements represented by the variables first and second ; when the value of either is changed, myWorker.postMessage([first.value,second.value]) is used to send the value inside both to the worker, as an array. You can send pretty much anything you like in the message. In the worker, we can respond when the message is received by writing an event handler block like this ( worker.js ): js onmessage = (e) => { console.log("Message received from main script"); const workerResult = `Result: ${e.data[0] * e.data[1]}`; console.log("Posting message back to main script"); postMessage(workerResult); }; The onmessage handler allows us to run some code whenever a message is received, with the message itself being available in the message event's data attribute. Here we multiply together the two numbers then use postMessage() again, to post the result back to the main thread. Back in the main thread, we use onmessage again, to respond to the message sent back from the worker: js myWorker.onmessage = (e) => { result.textContent = e.data; console.log("Message received from worker"); }; Here we grab the message event data and set it as the textContent of the result paragraph, so the user can see the result of the calculation. Note: Notice that onmessage and postMessage() need to be hung off the Worker object when used in the main script thread, but not when used in the worker. This is because, inside the worker, the worker is effectively the global scope. Note: When a message is passed between the main thread and worker, it is copied or "transferred" (moved), not shared. Read Transferring data to and from workers: further details for a much more thorough explanation. Terminating a worker If you need to immediately terminate a running worker from the main thread, you can do so by calling the worker's terminate method: js myWorker.terminate(); The worker thread is killed immediately. Handling errors When a runtime error occurs in the worker, its onerror event handler is called. It receives an event named error which implements the ErrorEvent interface. The event doesn't bubble and is cancelable; to prevent the default action from taking place, the worker can call the error event's preventDefault() method. The error event has the following three fields that are of interest: message A human-readable error message. filename The name of the script file in which the error occurred. lineno The line number of the script file on which the error occurred. Spawning subworkers Workers may spawn more workers if they wish. So-called sub-workers must be hosted within the same origin as the parent page. Also, the URIs for subworkers are resolved relative to the parent worker's location rather than that of the owning page. This makes it easier for workers to keep track of where their dependencies are. Importing scripts and libraries Worker threads have access to a global function, importScripts() , which lets them import scripts. It accepts zero or more URIs as parameters to resources to import; all the following examples are valid: js importScripts(); /* imports nothing */ importScripts("foo.js"); /* imports just "foo.js" */ importScripts("foo.js", "bar.js"); /* imports two scripts */ importScripts( "//example.com/hello.js", ); /* You can import scripts from other origins */ The browser loads each listed script and executes it. Any global objects from each script may then be used by the worker. If the script can't be loaded, NETWORK_ERROR is thrown, and subsequent code will not be executed. Previously executed code (including code deferred using setTimeout() ) will still be functional though. Function declarations after the importScripts() method are also kept, since these are always evaluated before the rest of the code. Note: Scripts may be downloaded in any order, but will be executed in the order in which you pass the filenames into importScripts() . This is done synchronously; importScripts() does not return until all the scripts have been loaded and executed. Shared workers A shared worker is accessible by multiple scripts — even if they are being accessed by different windows, iframes or even workers. In this section we'll discuss the JavaScript found in our Basic shared worker example ( run shared worker ): This is very similar to the basic dedicated worker example, except that it has two functions available handled by different script files: multiplying two numbers , or squaring a number . Both scripts use the same worker to do the actual calculation required. Here we'll concentrate on the differences between dedicated and shared workers. Note that in this example we have two HTML pages, each with JavaScript applied that uses the same single worker file. Note: If SharedWorker can be accessed from several browsing contexts, all those browsing contexts must share the exact same origin (same protocol, host, and port). Note: In Firefox, shared workers cannot be shared between documents loaded in private and non-private windows ( Firefox bug 1177621 ). Spawning a shared worker Spawning a new shared worker is pretty much the same as with a dedicated worker, but with a different constructor name (see index.html and index2.html ) — each one has to spin up the worker using code like the following: js const myWorker = new SharedWorker("worker.js"); One big difference is that with a shared worker you have to communicate via a port object — an explicit port is opened that the scripts can use to communicate with the worker (this is done implicitly in the case of dedicated workers). The port connection needs to be started either implicitly by use of the onmessage event handler or explicitly with the start() method before any messages can be posted. Calling start() is only needed if the message event is wired up via the addEventListener() method. Note: When using the start() method to open the port connection, it needs to be called from both the parent thread and the worker thread if two-way communication is needed. Sending messages to and from a shared worker Now messages can be sent to the worker as before, but the postMessage() method has to be invoked through the port object (again, you'll see similar constructs in both multiply.js and square.js ): js squareNumber.onchange = () => { myWorker.port.postMessage([squareNumber.value, squareNumber.value]); console.log("Message posted to worker"); }; Now, on to the worker. There is a bit more complexity here as well ( worker.js ): js onconnect = (e) => { const port = e.ports[0]; port.onmessage = (e) => { const workerResult = `Result: ${e.data[0] * e.data[1]}`; port.postMessage(workerResult); }; }; First, we use an onconnect handler to fire code when a connection to the port happens (i.e., when the onmessage event handler in the parent thread is set up, or when the start() method is explicitly called in the parent thread). We use the ports attribute of this event object to grab the port and store it in a variable. Next, we add an onmessage handler on the port to do the calculation and return the result to the main thread. Setting up this onmessage handler in the worker thread also implicitly opens the port connection back to the parent thread, so the call to port.start() is not actually needed, as noted above. Finally, back in the main script, we deal with the message (again, you'll see similar constructs in both multiply.js and square.js ): js myWorker.port.onmessage = (e) => { result2.textContent = e.data; console.log("Message received from worker"); }; When a message comes back through the port from the worker, we insert the calculation result inside the appropriate result paragraph. About thread safety The Worker interface spawns real OS-level threads, and mindful programmers may be concerned that concurrency can cause "interesting" effects in your code if you aren't careful. However, since web workers have carefully controlled communication points with other threads, it's actually very hard to cause concurrency problems. There's no access to non-thread-safe components or the DOM. And you have to pass specific data in and out of a thread through serialized objects. So you have to work really hard to cause problems in your code. Content security policy Workers are considered to have their own execution context, distinct from the document that created them. For this reason they are, in general, not governed by the content security policy of the document (or parent worker) that created them. So for example, suppose a document is served with the following header: http Content-Security-Policy: script-src 'self' Among other things, this will prevent any scripts it includes from using eval() . However, if the script constructs a worker, code running in the worker's context will be allowed to use eval() . To specify a content security policy for the worker, set a Content-Security-Policy response header for the request which delivered the worker script itself. The exception to this is if the worker script's origin is a globally unique identifier (for example, if its URL has a scheme of data or blob). In this case, the worker does inherit the CSP of the document or worker that created it. Transferring data to and from workers: further details Data passed between the main page and workers is copied , not shared (except for certain objects that can be explicitly shared ). Objects are serialized as they're handed to the worker, and subsequently, de-serialized on the other end. The page and worker do not share the same instance , so the end result is that a duplicate is created on each end. Most browsers implement this feature as structured cloning . As you probably know by now, data is exchanged between the two threads via messages using postMessage() , and the message event's data attribute contains data passed back from the worker. example.html : (the main page): js const myWorker = new Worker("my_task.js"); myWorker.onmessage = (event) => { console.log(`Worker said : "${event.data}"`); }; myWorker.postMessage({ lastUpdate: new Date() }); my_task.js (the worker): js self.onmessage = (event) => { postMessage(`Last updated: ${event.data.lastUpdate.toDateString()}`); }; The structured cloning algorithm can accept JSON and a few things that JSON can't — like circular references. Passing data examples Example 1: Advanced passing JSON Data and creating a switching system If you have to pass some complex data and have to call many different functions both on the main page and in the Worker, you can create a system which groups everything together. First, we create a QueryableWorker class that takes the URL of the worker, a default listener, and an error handler, and this class is going to keep track of a list of listeners and help us communicate with the worker: js function QueryableWorker(url, defaultListener, onError) { const worker = new Worker(url); const listeners = {}; this.defaultListener = defaultListener ?? (() => {}); if (onError) { worker.onerror = onError; } this.postMessage = (message) => { worker.postMessage(message); }; this.terminate = () => { worker.terminate(); }; } Then we add the methods of adding/removing listeners: js this.addListeners = (name, listener) => { listeners[name] = listener; }; this.removeListeners = (name) => { delete listeners[name]; }; Here we let the worker handle two simple operations for illustration: getting the difference of two numbers and making an alert after three seconds. In order to achieve that we first implement a sendQuery method which queries if the worker actually has the corresponding methods to do what we want. js // This functions takes at least one argument, the method name we want to query. // Then we can pass in the arguments that the method needs. this.sendQuery = (queryMethod, ...queryMethodArguments) => { if (!queryMethod) { throw new TypeError( "QueryableWorker.sendQuery takes at least one argument", ); } worker.postMessage({ queryMethod, queryMethodArguments, }); }; We finish QueryableWorker with the onmessage method. If the worker has the corresponding methods we queried, it should return the name of the corresponding listener and the arguments it needs, we just need to find it in listeners .: js worker.onmessage = (event) => { if ( event.data instanceof Object && Object.hasOwn(event.data, "queryMethodListener") && Object.hasOwn(event.data, "queryMethodArguments") ) { listeners[event.data.queryMethodListener].apply( this, event.data.queryMethodArguments, ); } else { this.defaultListener(event.data); } }; Now onto the worker. First we need to have the methods to handle the two simple operations: js const queryableFunctions = { getDifference(a, b) { reply("printStuff", a - b); }, waitSomeTime() { setTimeout(() => { reply("doAlert", 3, "seconds"); }, 3000); }, }; function reply(queryMethodListener, ...queryMethodArguments) { if (!queryMethodListener) { throw new TypeError("reply - takes at least one argument"); } postMessage({ queryMethodListener, queryMethodArguments, }); } // This method is called when main page calls QueryWorker's postMessage // method directly function defaultReply(message) { // do something } And the onmessage method is now trivial: js onmessage = (event) => { if ( event.data instanceof Object && Object.hasOwn(event.data, "queryMethod") && Object.hasOwn(event.data, "queryMethodArguments") ) { queryableFunctions[event.data.queryMethod].apply( self, event.data.queryMethodArguments, ); } else { defaultReply(event.data); } }; Here are the full implementation: example.html (the main page): html <ul> <li> <button id="first-action">What is the difference between 5 and 3?</button> </li> <li> <button id="second-action">Wait 3 seconds</button> </li> <li> <button id="terminate">terminate() the Worker</button> </li> </ul> It needs to execute the following script, either inline or as an external file: js // QueryableWorker instances methods: // * sendQuery(queryable function name, argument to pass 1, argument to pass 2, etc. etc.): calls a Worker's queryable function // * postMessage(string or JSON Data): see Worker.prototype.postMessage() // * terminate(): terminates the Worker // * addListener(name, function): adds a listener // * removeListener(name): removes a listener // QueryableWorker instances properties: // * defaultListener: the default listener executed only when the Worker calls the postMessage() function directly function QueryableWorker(url, defaultListener, onError) { const worker = new Worker(url); const listeners = {}; this.defaultListener = defaultListener ?? (() => {}); if (onError) { worker.onerror = onError; } this.postMessage = (message) => { worker.postMessage(message); }; this.terminate = () => { worker.terminate(); }; this.addListener = (name, listener) => { listeners[name] = listener; }; this.removeListener = (name) => { delete listeners[name]; }; // This functions takes at least one argument, the method name we want to query. // Then we can pass in the arguments that the method needs. this.sendQuery = (queryMethod, ...queryMethodArguments) => { if (!queryMethod) { throw new TypeError( "QueryableWorker.sendQuery takes at least one argument", ); } worker.postMessage({ queryMethod, queryMethodArguments, }); }; worker.onmessage = (event) => { if ( event.data instanceof Object && Object.hasOwn(event.data, "queryMethodListener") && Object.hasOwn(event.data, "queryMethodArguments") ) { listeners[event.data.queryMethodListener].apply( this, event.data.queryMethodArguments, ); } else { this.defaultListener(event.data); } }; } // your custom "queryable" worker const myTask = new QueryableWorker("my_task.js"); // your custom "listeners" myTask.addListener("printStuff", (result) => { document .getElementById("firstLink") .parentNode.appendChild( document.createTextNode(`The difference is ${result}!`), ); }); myTask.addListener("doAlert", (time, unit) => { alert(`Worker waited for ${time} ${unit} :-)`); }); document.getElementById("first-action").addEventListener("click", () => { myTask.sendQuery("getDifference", 5, 3); }); document.getElementById("second-action").addEventListener("click", () => { myTask.sendQuery("waitSomeTime"); }); document.getElementById("terminate").addEventListener("click", () => { myTask.terminate(); }); my_task.js (the worker): js const queryableFunctions = { // example #1: get the difference between two numbers: getDifference(minuend, subtrahend) { reply("printStuff", minuend - subtrahend); }, // example #2: wait three seconds waitSomeTime() { setTimeout(() => { reply("doAlert", 3, "seconds"); }, 3000); }, }; // system functions function defaultReply(message) { // your default PUBLIC function executed only when main page calls the queryableWorker.postMessage() method directly // do something } function reply(queryMethodListener, ...queryMethodArguments) { if (!queryMethodListener) { throw new TypeError("reply - not enough arguments"); } postMessage({ queryMethodListener, queryMethodArguments, }); } onmessage = (event) => { if ( event.data instanceof Object && Object.hasOwn(event.data, "queryMethod") && Object.hasOwn(event.data, "queryMethodArguments") ) { queryableFunctions[event.data.queryMethod].apply( self, event.data.queryMethodArguments, ); } else { defaultReply(event.data); } }; It is possible to switch the content of each mainpage -> worker and worker -> mainpage message. And the property names "queryMethod", "queryMethodListeners", "queryMethodArguments" can be anything as long as they are consistent in QueryableWorker and the worker . Passing data by transferring ownership (transferable objects) Modern browsers contain an additional way to pass certain types of objects to or from a worker with high performance. Transferable objects are transferred from one context to another with a zero-copy operation, which results in a vast performance improvement when sending large data sets. For example, when transferring an ArrayBuffer from your main app to a worker script, the original ArrayBuffer is cleared and no longer usable. Its content is (quite literally) transferred to the worker context. js // Create a 32MB "file" and fill it with consecutive values from 0 to 255 – 32MB = 1024 * 1024 * 32 const uInt8Array = new Uint8Array(1024 * 1024 * 32).map((v, i) => i); worker.postMessage(uInt8Array.buffer, [uInt8Array.buffer]); Sharing data The SharedArrayBuffer object allows two threads, such as the worker and the main thread, to simultaneously operate on the same memory span and exchange data without going through the messaging mechanism. Using shared memory does come with significant determinism, security, and performance concerns, some of which are outlined in the JavaScript execution model article. Embedded workers There is not an "official" way to embed the code of a worker within a web page, like <script> elements do for normal scripts. But a <script> element that does not have a src attribute and has a type attribute that does not identify an executable MIME type can be considered a data block element that JavaScript could use. "Data blocks" is a more general feature of HTML that can carry almost any textual data. So, a worker could be embedded in this way: html <!doctype html> <html lang="en-US"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width" /> <title>MDN Example - Embedded worker</title> <script type="text/js-worker"> // This script WON'T be parsed by JS engines because its MIME type is text/js-worker. const myVar = "Hello World!"; // Rest of your worker code goes here. </script> <script> // This script WILL be parsed by JS engines because its MIME type is text/javascript. function pageLog(sMsg) { // Use a fragment: browser will only render/reflow once. const frag = document.createDocumentFragment(); frag.appendChild(document.createTextNode(sMsg)); frag.appendChild(document.createElement("br")); document.querySelector("#logDisplay").appendChild(frag); } </script> <script type="text/js-worker"> // This script WON'T be parsed by JS engines because its MIME type is text/js-worker. onmessage = (event) => { postMessage(myVar); }; // Rest of your worker code goes here. </script> <script> // This script WILL be parsed by JS engines because its MIME type is text/javascript. // In the past blob builder existed, but now we use Blob const blob = new Blob( Array.prototype.map.call( document.querySelectorAll("script[type='text/js-worker']"), (script) => script.textContent, ), { type: "text/javascript" }, ); // Creating a new global "worker" variable from all our "text/js-worker" scripts. const worker = new Worker(window.URL.createObjectURL(blob)); worker.onmessage = (event) => { pageLog(`Received: ${event.data}`); }; </script> </head> <body> <div id="logDisplay"></div> <script> // Start the worker. worker.postMessage(""); </script> </body> </html> The embedded worker is now nested into a new custom document.worker property. It is also worth noting that you can also convert a function into a Blob, then generate an object URL from that blob. For example: js function fn2workerURL(fn) { const blob = new Blob([`(${fn.toString()})()`], { type: "text/javascript" }); return URL.createObjectURL(blob); } Further examples This section provides further examples of how to use web workers. Performing computations in the background Workers are mainly useful for allowing your code to perform processor-intensive calculations without blocking the user interface thread. In this example, a worker is used to calculate Fibonacci numbers. The JavaScript code The following JavaScript code is stored in the "fibonacci.js" file referenced by the HTML in the next section. js self.onmessage = (event) => { const userNum = Number(event.data); self.postMessage(fibonacci(userNum)); }; function fibonacci(num) { let a = 1; let b = 0; while (num > 0) { [a, b] = [a + b, a]; num--; } return b; } The worker sets the property onmessage to a function which will receive messages sent when the worker object's postMessage() is called. This performs the math and eventually returns the result back to the main thread. The HTML code html <form> <div> <label for="number"> Enter a number that is a zero-based index position in the fibonacci sequence to see what number is in that position. For example, enter 6 and you'll get a result of 8 — the fibonacci number at index position 6 is 8. </label> <input type="number" id="number" /> </div> <div> <input type="submit" /> </div> </form> <p id="result"></p> It needs to execute the following script, either inline or as an external file: js const form = document.querySelector("form"); const input = document.querySelector('input[type="number"]'); const result = document.querySelector("p#result"); const worker = new Worker("fibonacci.js"); worker.onmessage = (event) => { result.textContent = event.data; console.log(`Got: ${event.data}`); }; worker.onerror = (error) => { console.log(`Worker error: ${error.message}`); throw error; }; form.onsubmit = (e) => { e.preventDefault(); worker.postMessage(input.value); input.value = ""; }; The web page creates a <p> element with the ID result , which gets used to display the result, then spawns the worker. After spawning the worker, the onmessage handler is configured to display the results by setting the contents of the <p> element, and the onerror handler is set to log the error message to the devtools console. Finally, a message is sent to the worker to start it. Try this example live . Dividing tasks among multiple workers As multicore computers become increasingly common, it's often useful to divide computationally complex tasks among multiple workers, which may then perform those tasks on multiple-processor cores. Other types of workers In addition to dedicated and shared web workers, there are other types of workers available: ServiceWorkers essentially act as proxy servers that sit between web applications, and the browser and network (when available). They are intended to (amongst other things) enable the creation of effective offline experiences, intercepting network requests and taking appropriate action based on whether the network is available and updated assets reside on the server. They will also allow access to push notifications and background sync APIs. Audio Worklet provide the ability for direct scripted audio processing to be done in a worklet (a lightweight version of worker) context. Debugging worker threads Most browsers enable you to debug web workers in their JavaScript debuggers in exactly the same way as debugging the main thread! For example, both Firefox and Chrome list JavaScript source files for both the main thread and active worker threads, and all of these files can be opened to set breakpoints and logpoints. To learn how to debug web workers, see the documentation for each browser's JavaScript debugger: Chrome Sources panel Firefox JavaScript Debugger To open devtools for web workers, you can use the following URLs: Edge: edge://inspect/ Chrome: chrome://inspect/ Firefox: about:debugging#/runtime/this-firefox These pages show an overview over all service workers. You need to find the relevant one by the URL and then click inspect to access devtools such as the console and debugger for that worker. Functions and interfaces available in workers You can use most standard JavaScript features inside a web worker, including: Navigator fetch() Array , Date , Math , and String setTimeout() and setInterval() The main thing you can't do in a Worker is directly affect the parent page. This includes manipulating the DOM and using that page's objects. You have to do it indirectly, by sending a message back to the main script via DedicatedWorkerGlobalScope.postMessage() , then doing the changes in event handler. Note: You can test whether a method or interface is available to workers using the Worker Playground . Note: For a complete list of functions available to workers, see Functions and interfaces available to workers . Specifications Specification HTML # workers See also Worker interface SharedWorker interface Functions available to workers OffscreenCanvas interface Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Sep 11, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Web Workers API Guides Using Web Workers Functions and classes available to Web Workers The structured clone algorithm Transferable objects Interfaces DedicatedWorkerGlobalScope SharedWorker SharedWorkerGlobalScope Worker WorkerGlobalScope WorkerLocation WorkerNavigator Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/user-preferences#setting-up-preference-categories | User Preferences - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences User Preferences Tenant Preferences Preference Evaluation Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Preferences User Preferences Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Preferences User Preferences OpenAI Open in ChatGPT Learn how user preferences work in SuprSend and how to capture them. OpenAI Open in ChatGPT Before you start: Make sure you’ve set up notification categories first. See Manage Categories and Preferences for step-by-step instructions. Preferences let users control which notifications they receive. Instead of an all-or-nothing approach, users can opt out of specific categories, choose preferred channels, and set notification frequency. This granular control reduces the chance that users disable all notifications from your platform. In SuprSend, you can use ready-made UI and APIs to manage multi-tenant preference use cases. This includes letting admins set preferences for internal teams and handle notifications for enterprise customers, where companies, customers, and end users have distinct preferences. How It Works Preferences are evaluated in priority order: User Preference → Tenant Default → Category Default Three Levels of Control Global channel opt-outs, category preferences, and channel opt-outs within categories What are user preferences? Preferences only work with sub-categories: User preferences apply to sub-categories you create, not root-categories (System, Transactional, Promotional). Use sub-category slugs in workflows for preferences to work. Each user has a preference set that controls which notifications they receive. A preference set has three levels of control: channel_preferences — Global channel opt-outs (e.g., opt out of all email) categories — Category-level preferences (opt in/out of all channels of a notification type) opt_out_channels — Opt-in/out of specific channels within a category Example: Copy Ask AI { "channel_preferences" : [ { "channel" : "email" , "is_restricted" : true } ], "categories" : [ { "category" : "invoice-ready" , "preference" : "opt_out" }, { "category" : "payment-reminder" , "preference" : "opt_in" , "opt_out_channels" : [ "slack" ] } ] } In this example: user opted out of email globally, opted out of invoice-ready category completely, and stays opted in to payment-reminder but without Slack. How preferences are determined When a user hasn’t set their own preferences in a category, SuprSend uses defaults in this order: User Preference — Individual user’s explicit choices (highest priority) Tenant Default Preference — Default preferences set by tenant for the category Category Default Preference — Default preferences set at the category level (lowest priority) Preference precedence: User Preference → Tenant Default Preference → Category Default Preference Preference precedence is determined at category level . So, if a user overrides preference for a category but doesn’t touch other categories, defaults continue to apply to the untouched categories. Setting up preference categories Before users can set their preferences, you must first create and configure preference categories. For step-by-step setup instructions, see Manage Categories and Preferences . Default preferences Default preferences determine how users receive notifications when they haven’t set their own preferences. Configure these at the sub-category level when setting up categories. What default preferences control Default preferences control: Channel or Category defaults : Which categories or channels will be turned on/off by default on users’ preference page. Mandatory channels : Which channel or category users cannot opt out of (shown as disabled on preference page) Visibility : Whether a category appears on the preference page Preference types On — Users receive this category's notifications by default Users will receive notifications in this category by default. You can configure Opt-in Channels to specify which channels are included in the default “On” state: All : All available channels are enabled by default Selected Channels only : Only specific channels you select are enabled by default (e.g., Email, Android Push, iOS Push, In-App Inbox, MS Teams, Slack) Off — Users must opt in to get notifications Users will not receive notifications unless they change the preference. Can't Unsubscribe — Users cannot opt out of mandatory channels in this category Prevents users from fully opting out of the category. When selected, you can configure: Mandatory Channels : Channels which can’t be opted out of by the user. Set to “All” or “Selected Channels”. Opt-in Channels : In case of “Selected” Mandatory Channels, you can configure the channels that will be opted in by default. Channels other than mandatory and opt-in will be skipped for sending notification unless user explicitly opts in to them. Even when a category is set to “Can’t Unsubscribe,” users can still control channel-level preferences if your channel-level settings allow it. This configuration gives you fine-grained control over which channels a user is opted into by default, letting you differentiate between must-deliver channels, default-on channels, and optional channels. Capturing user preferences Users can set their preferences through one of the following methods: Hosted preference page Once you publish preference categories, SuprSend automatically generates a dedicated unsubscription webpage for collecting user preferences . Users can set channel-specific preferences from the hosted page. If the link is included in an email, the hosted page will show and save email preferences. Include it in your templates using {{$hosted_preference_url}} . This page is currently hosted on a SuprSend domain, but you can reach out to [email protected] if you’d prefer it hosted on your own domain. Embed in your product You can embed the preference interface directly inside your product using SuprSend’s ready-made UI components. SDKs exist in the languages below. Update your product preference page link on the tenant page and render it in templates using {{$embedded_preference_url}} . Javascript React Angular Embeddable preference page Controlling what categories to show on UI It’s always a good practice to show only the categories that are relevant to the user. There are two ways to achieve this: Hide categories for tenant users In a multi-tenant setup, tenants or admins can control which categories their users see. Setting visible_to_subscriber: false in tenant preferences hides the category from tenant users’ preference pages. Hidden categories won’t send notifications to those users, even if they previously opted in. Filter categories with tags Use tags to show categories based on user roles, departments, or teams. Filter categories in the preference center using the tags query parameter. 1 Setting Preference tags Tags can be added to sections and sub-categories directly from Developers → Notification Categories in the SuprSend Console. When a tag is assigned at the section level, it automatically applies to all categories under that section—so filtering by a section tag also filters its child categories. 2 Filter Categories with Tags You can filter categories using the tags query parameter in the API. This can be a simple tag match (e.g. tags=tag1 ) or a more advanced filter using logical operators. Supported operators: Operator Operand Datatype Description Example exists boolean Returns categories where any tag is set tags={ "exists": true } not string Excludes categories that have the specified tag tags={ "not": "admin" } or array Returns categories that match any of the provided tags tags={ "or": ["sales", "marketing"] } and array Returns categories that match all provided tags tags={ "and": ["sales", "manager"] } You can combine these operators for nested filtering like tags={ "or": [{ "and": ["sales", "manager"] }, { "and": ["marketing", "associate"] }] } . If no tags are provided, the preference center returns all visible categories. For details on how tags work, see Tags . Translating preference categories in user’s locale Upload translation files for your category names and descriptions. See How to manage Category translations for details. Once uploaded, pass a locale parameter (e.g., es , fr , de ) when: Loading the embeddable preference center As a query parameter in the get user preference API . The hosted preference page picks the locale from user’s profile. On hosted preference page, Dynamic content (category names, descriptions) is translated using translation files you upload. Static content (CTA text, labels, buttons, etc.) is translated automatically using SuprSend’s built-in i18n support for commonly used languages. You can see the list of supported languages below. Supported languages Language Code English en Spanish es French fr German de Italian it Portuguese pt Catalan ca Russian ru Dutch nl Polish pl Japanese ja Vietnamese vi Language Code Indonesian id Korean ko Serbian sr Norwegian no Hebrew he Chinese zh Finnish fi Swedish sv Czech cs Lithuanian lt Arabic ar How preferences are evaluated SuprSend evaluates user preferences at send time. For every recipient, the system checks user-level preferences first, then tenant-level overrides, and finally category defaults. For detailed information on the evaluation process, see Preference Evaluation . Other ways to unsubcribe from notifications In addition to the preference center within SuprSend, communication channels provide their own opt-out options, which SuprSend manages internally. Email: Unsubscribe URL header Gmail requires an unsubscribe URL in email headers when sending bulk emails (5,000+ emails/day). Most email providers expect you to add your own unsubscription page or offer a basic all-or-nothing opt-out option. You can add {{$hosted_preference_url}} here to load the SuprSend hosted preference page from the email header. Inbox (In-App): Render preference page inside your Inbox Companies also give users the option to load preference settings inside their in-app Inbox or provide a link to redirect users to the Preference center in their product. Mobile Push: Preference Page in App settings For mobile push notifications, users typically manage their preferences through the app settings. The category you assign in your workflow is also sent as the push “category” (used by Android/iOS to group notifications). If you set preference categories, the system automatically reflects them in the user’s app settings, loading similar preference controls. SMS & Whatsapp: Reply `STOP` Users generally unsubscribe from Short Message Service (SMS) by replying “STOP.” SuprSend automatically marks the SMS channel as inactive in the user’s profile when it receives a STOP reply. For WhatsApp, opt-out behavior depends on the provider; where supported, users can reply STOP and SuprSend will mark the channel inactive. FAQ How do I set up a digest schedule? You can create sub-categories for different digest schedules or set the digest schedule in the user profile and pass a dynamic schedule in the workflow digest node. An option to set the digest schedule directly on your preference page will be available soon. I have a use case where a company has multiple departments/roles, and the admin will set preferences for users in these departments. You can manage this with tenant preferences. In the SuprSend system, each tenant represents an organization, and the administrator sets which categories to send to their internal team using the tenant preference API . What happens to existing user preference view if I change default preference setting? Changing the default preference for a category doesn’t affect users who have already made changes to that category. For categories where users haven’t made any changes, the preferences update according to the new default settings. I have multiple enterprise customers with various product offerings. Customers should only receive notifications for the products they have enabled, and the same should be visible on their preference page. How can I manage this in SuprSend? You can turn off categories for tenants from the tenant page on the SuprSend console. Turning off the preference for a category automatically removes it from the tenant preference APIs and UI view. To further apply this to the tenant’s users, set visible to subscriber to false in the default tenant preferences to hide the category from the tenant’s end users. Why don't I see the 'inbox' channel in my user preferences? The inbox channel preference is behind a feature flag and needs to be enabled for your account. If you don’t see the inbox channel in your user preferences, contact [email protected] to have the feature flag enabled for your workspace. Why do users still receive promotional notifications even after unsubscribing from all categories? Unsubscribing from top-level categories (System, Transactional, Promotional) is not supported . Preferences only work with sub-categories you create. If you’re sending notifications using a top-level category like "promotional" in your workflows, users cannot unsubscribe from those notifications through the preference center, even if they unsubscribe from all visible categories. Solution: Create sub-categories under the Promotional category (e.g., “Marketing”, “Newsletter”, “Product Updates”) and use those sub-category slugs in your workflows instead of the top-level category. This allows users to: See and control preferences for each notification type Opt out of specific sub-categories Have their preferences respected when you send notifications Best practice: Organize notifications into meaningful sub-categories rather than using top-level categories directly. This provides users with granular control and improves their experience. Can I use user preferences in workflow branching to control which notifications are sent? User preferences are not passed in the workflow payload, so you cannot directly access them in branch conditions or other workflow nodes. Workaround: If you need to use preference-based logic in workflows (e.g., to route notifications based on user preferences or combine multiple notification scenarios in a single workflow), you can: Store the same preference data as custom properties in the user profile Use those custom properties in branch conditions to route notifications Example use case: If you want to combine multiple notification scenarios (e.g., “New Comment”, “Reply on my comment”, “I am mentioned”) in a single workflow to avoid duplicate notifications, you can: Store user preferences for each scenario as custom properties (e.g., wants_new_comment_notifications: true , wants_mention_notifications: true ) Use branch conditions to check these properties and route notifications accordingly This allows you to have one workflow that handles all scenarios while respecting user preferences Alternative approach: Create separate workflows for each notification scenario with conditions in the Trigger node. Each workflow can use its own preference category, allowing users to control each scenario independently. How do I let users control both notification on/off and the time they want to be reminded (e.g., medicine reminders)? You can combine preference categories with dynamic digest schedules to achieve this: 1. Set up preference categories: Create a preference category (e.g., “medicine-reminders”) that users can opt in/out of using the preference APIs or preference center UI . 2. Store time preference as user property: When users select their preferred reminder time, store it as a custom property in their user profile. For example: Copy Ask AI user.set({ "medicineReminderTime" : { "frequency" : "daily" , "time" : "09:00" , "tz_selection" : "recipient" } }) 3. Use dynamic schedule in digest node: In your workflow’s digest node, configure it to use a dynamic schedule that references the user property (e.g., ."$recipient".medicineReminderTime ). The digest will only send if the user has opted in to the category, and it will send at their preferred time. Implementation flow: Client side (React Native) : Capture user’s time preference and call your backend API Server side (Supabase Edge Function) : Update both the user’s preference (opt in/out) via SuprSend preference API and store the time preference as a user property Workflow : Use preference category to control on/off, and dynamic schedule to control timing For detailed information, see Dynamic Schedule in the digest documentation. Related documentation Notification Categories - Setting up categories & defaults Manage Categories and Preferences - Complete guide to setting up and managing categories and preferences Tenant Preferences - Managing tenant-level preferences Preference Evaluation - How SuprSend evaluates preferences at runtime Was this page helpful? Yes No Suggest edits Raise issue Previous Tenant Preferences Learn how to manage preferences for your tenants and their users. Next ⌘ I x github linkedin youtube Powered by On this page What are user preferences? How preferences are determined Setting up preference categories Default preferences What default preferences control Preference types Capturing user preferences Hosted preference page Embed in your product Controlling what categories to show on UI Hide categories for tenant users Filter categories with tags Translating preference categories in user’s locale How preferences are evaluated Other ways to unsubcribe from notifications FAQ Related documentation | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/Structuring_content | Structuring content with HTML - Learn web development | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Learn Core learning modules HTML Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Structuring content with HTML Overview: Core learning modules Next HTML is the technology that defines the content and structure of any website. Written properly, it should also define the semantics (meaning) of the content in a machine-readable way, which is vital for accessibility, search engine optimization, and making use of the built-in features browsers provide for content to work optimally. This module covers the basics of the language, before looking at key areas such as document structure, links, lists, images, forms, and more. In this article Prerequisites Tutorials and challenges Test your skills Additional tutorials See also Prerequisites Before starting this module, you don't need any previous HTML knowledge, but you should have at least basic familiarity with using computers and using the web passively (i.e., just looking at it and consuming content). You should have a basic work environment set up (as detailed in Installing basic software ), and understand how to create and manage files (as detailed in Dealing with files ). Both are parts of our Getting started with the web complete beginner's module. Note: If you are working on a computer, tablet, or another device where you can't create files, you can try running the code in an online editor such as CodePen or JSFiddle . Tutorials and challenges Basic HTML syntax Covers the absolute basics of HTML , to get you started — we define elements, attributes, and other important terms, and show where they fit in the language. We also show how a typical HTML page is structured and how an HTML element is structured, and explain other important basic language features. Along the way, we'll play with some HTML to get you interested! What's in the head? Web page metadata The head of an HTML document is the part that is not displayed in the web browser when the page is loaded. It contains metadata information such as the page <title> , links to CSS (if you want to style your HTML content with CSS), links to custom favicons, and metadata (data about the HTML, such as who wrote it, and important keywords that describe the document). Headings and paragraphs One of HTML's main jobs is to give text structure so that a browser can display an HTML document the way its developer intends. This article explains how HTML can be used to provide fundamental page structure by defining headings and paragraphs. Emphasis and importance The previous article looked at why semantics are important in HTML, and focused on headings and paragraphs. This article continues on the theme of semantics, looking at HTML elements that apply emphasis and importance to text (parallel to italics and bold text in print media). Lists Lists are everywhere in life—from your shopping list to the list of directions you subconsciously follow to get to your house every day, to the lists of instructions you are following in these tutorials! It may not surprise you that HTML has a convenient set of elements that allows us to define different types of list. On the web, we have three types of lists: unordered, ordered, and description lists. This lesson shows you how to use the different types. Advanced text features There are many other elements in HTML for defining text semantics, which we didn't get to in the Emphasis and importance article. The elements described in this article are less known, but still useful to know about (and this is still not a complete list by any means). Here you'll learn about marking up quotations, computer code and other related text, subscript and superscript, contact information, and more. Marking up a letter Challenge We all learn to write a letter sooner or later; it is also a useful example to test our text formatting skills. In this challenge, you'll have a letter to mark up as a test for your HTML text formatting skills, as well as hyperlinks and proper use of the HTML <head> element. Structuring documents In addition to defining individual parts of your page (such as "a paragraph" or "an image"), HTML also boasts a number of block level elements used to define areas of your website (such as "the header", "the navigation menu", "the main content column"). This article looks into how to plan a basic website structure, and write the HTML to represent this structure. Creating links Links (also known as hyperlinks) are really important — they are what makes the Web a web . This article shows the syntax required to make a link, and discusses link best practices. Structuring a page of content Challenge Structuring a page of content ready for laying it out using CSS is a very important skill to master, so in this challenge you'll be tested on your ability to think about how a page might end up looking, and choose appropriate structural semantics to build a layout on top of. HTML images In the beginning, the web was just text, and it was really quite boring. Fortunately, it wasn't too long before the ability to embed images (and other more interesting types of content) inside web pages was added. In this article we'll look at how to use the <img> element in depth, including the basics, annotating it with captions using <figure> , and detailing how it relates to CSS background images. HTML video and audio Now that we are comfortable with adding simple images to a webpage, the next step is to start adding video and audio players to your HTML documents! In this article we'll look at doing just that with the <video> and <audio> elements; we'll then finish off by looking at how to add captions/subtitles to your videos. Creepy-crawly splash page Challenge In this challenge, we'll test your knowledge of some of the techniques discussed in the last couple of lessons, getting you to add some images and video to a splash page all about bugs and other creepy crawlies. HTML table basics This article gets you started with HTML tables, covering the very basics such as rows, cells, headings, making cells span multiple columns and rows, and how to group together all the cells in a column for styling purposes. HTML table accessibility In this article we look at more HTML table accessibility features such as captions/summaries, grouping your rows into table head, body and footer sections, and scoping columns and rows. Structuring a planet data table Challenge In this challenge, we provide you with some data on the planets in our solar system. Your job is to structure it into an accessible HTML table. Forms and buttons in HTML HTML forms and buttons are powerful tools for interacting with users — most commonly they are used for collecting data from users or allowing them to control a user interface. In this article we provide an introduction to the basics of forms and buttons. Debugging HTML Writing HTML is fine, but what if something goes wrong, and you can't work out where the error in the code is? This article will introduce you to some tools that can help you find and fix errors in HTML. Test your skills You will find "Test your skills" articles placed between the tutorial articles to check whether you have retained the most important information before you move on. If you want to explore all of these together, you can find them listed at Test your skills: HTML . Additional tutorials These tutorials are not part of the learning pathway, but they are interesting nonetheless — you should consider these as stretch goals, to optionally study when you are done with the main Core articles. Including vector graphics in HTML Vector graphics are very useful in many circumstances — they have small file sizes and are highly scalable, so they don't pixelate when zoomed in or blown up to a large size. In this article we'll show you how to include one in your webpage. From object to iframe — general embedding technologies Developers commonly think of embedding media such as images, video and audio into web pages. In this article we take somewhat of a sideways step, looking at some elements that allow you to embed a wide variety of content types into your webpages: the <iframe> , <embed> and <object> elements. <iframe> s are for embedding other web pages, and the other two allow you to embed external resources such as PDF files. See also Learn HTML and CSS , Scrimba MDN learning partner Scrimba's Learn HTML and CSS course teaches you HTML and CSS through building and deploying five awesome projects, with fun interactive lessons and challenges taught by knowledgeable teachers. Learn HTML , Codecademy Another useful resource for learning HTML basics. The basics of semantic HTML , Scrimba MDN learning partner This interactive lesson provides a useful description of HTML, with particular emphasis on why the semantic aspect of it is important. Overview: Core learning modules Next Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Aug 28, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Learn web development MDN curriculum Getting started modules Environment setup Installing software Browsing the web Code editors Dealing with files Command line Your first website What will it look like? Creating the content Styling the content Adding interactivity Publishing Web standards How the web works The web standards model How browsers load websites Soft skills Research and learning Collaboration and teamwork Workflows and processes Finding a job Core modules Structuring content with HTML Basic HTML syntax Web page metadata Headings and paragraphs Emphasis and importance Lists Test: HTML text basics Advanced text features Test: Advanced HTML text Challenge: Letter markup Structuring documents Creating links Test: Links Challenge: Bird watching site Images Test: Images Video and audio Test: Audio and video Challenge: Splash page Table basics Table accessibility Challenge: Planet data table Forms and buttons Test: Forms and buttons Challenge: Feedback form Debugging HTML Test: HTML tests index Additional tutorials Vector graphics Embedding technologies CSS styling basics What is CSS? CSS getting started Challenge: Biography page Basic selectors Attribute selectors Pseudo-classes and elements Combinators Test: Selectors Box model Test: Box model Handling conflicts Test: Cascade Challenge: Fixing blog styles Values and units Test: Values and units Sizing Test: Sizing Backgrounds and borders Test: Backgrounds and borders Overflow Test: Overflow Challenge: Sizing and decorating Images, media, forms Test: Images and forms Styling tables Challenge: Styling color scheme search Debugging CSS Test: Styling basics tests index Additional tutorials Advanced styling effects Cascade layers Multiple text directions Organizing your CSS CSS text styling Text and font fundamentals Styling lists Styling links Web fonts Challenge: Community school homepage CSS layout Introduction Floats Test: Floats Positioning Test: Positioning Flexbox Test: Flexbox CSS grid layout Test: CSS grid Challenge: Fundamental layout Responsive web design Media queries Test: RWD & media queries Challenge: mobile-first Test: Layout tests index Additional tutorials Multiple-column layout Practical positioning examples Legacy layout methods Supporting older browsers Dynamic scripting with JavaScript What is JavaScript? JavaScript walkthrough Troubleshooting Variables Test: Variables Numbers and operators Test: Math Strings String methods Test: Strings Arrays Test: Arrays Challenge: Story generator Conditionals Test: Conditionals Loops Test: Loops Functions Build your own function Function return values Test: Functions Events Event bubbling Test: Events Objects Test: Objects DOM scripting Challenge: Image gallery Network requests JSON Test: JSON Challenge: House data UI Debugging and error handling Test: JavaScript tests index JavaScript frameworks and libraries Introduction Framework features React getting started React ToDo app React components React events and state React editing, filtering, conditional UI React accessibility React resources Accessibility What is accessibility? Accessibility tools Accessible HTML Test: HTML a11y Accessible CSS and JS Test: CSS/JS a11y WAI-ARIA Test: WAI-ARIA Accessible multimedia Mobile accessibility Challenge: A11y debugging Test: A11y tests index Design for developers Version control Extension modules Advanced JavaScript objects Object prototypes Object-oriented programming Classes in JavaScript Test: Object-oriented JavaScript Object building practice Challenge: Bouncing balls features Test: OOJS tests index Client-side web APIs Introduction Video and audio Drawing graphics Client-side storage Third-party APIs Asynchronous JavaScript Introduction Using promises Implementing promise-based APIs Introducing workers Challenge: Animation sequence Web forms Your first form How to structure a web form Basic native form controls The HTML5 input types Other form controls Styling web forms Advanced form styling Customizable selects UI pseudo-classes Client-side form validation Sending form data Additional tutorials Custom form controls JS form submission Forms in legacy browsers UI methods & controls Understanding client-side tools Overview Package management Sample toolchain Deploying our app Server-side websites First steps Introduction Client-server overview Server-side frameworks Website security Django (Python) Django introduction Dev environment setup 1: Local library tutorial 2: Skeleton website 3: Models 4: Django admin site 5: Home page 6: Generic list and detail views 7: Sessions framework 8: Authentication and permissions 9: Forms 10: Testing 11: Deploying Django security Challenge: Django blog Express (Node.js) Express/Node introduction Dev environment setup 1: Local library tutorial 2: Skeleton website 3: Using databases with Mongoose 4: Routes and controllers 5: Displaying data 6: Working with forms 7: Deploying Additional tutorials Apache .htaccess Server MIME type config Plain Node.js server Web performance The "why" of web performance What is web performance? Perceived performance Measuring performance Multimedia: Images Multimedia: video Performant JavaScript Performant HTML Performant CSS Performance business case Best practices & tips Testing Introduction Testing strategies Common HTML and CSS problems Feature detection Automated testing Automation environment setup Further resources How to solve common problems Common CSS problems Common HTML problems Common JavaScript problems Design and accessibility Tools and setup Web mechanics About Resources for educators Changelog Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/Performance | Web performance | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Performance Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Web performance Web performance is the objective measurements and the perceived user experience of load time and runtime. Web performance is how long a site takes to load, become interactive and responsive, and how smooth the content is during user interactions. Performance concerns questions like: Is scrolling smooth? Are buttons responsive? Do pop-ups load quickly and animate fluidly? The objective measurements include time to load, frames per second, and time to become interactive, and subjective experience means how long it feels like it takes for content to load. The longer it takes for a site to respond, the more users will abandon the site. It is important to minimize the loading and response times and add additional features to conceal latency by making the experience as available and interactive as possible, as soon as possible, while asynchronously loading in the longer tail parts of the experience. There are tools, APIs, and best practices that help us measure and improve web performance. We cover them in the following pages. In this article Web performance guides Tutorials for beginners Performance APIs Profiling and tooling References See also Web performance guides The Performance guides are resources that describe how browsers work, what affects performance, and how to measure, optimize, and monitor performance across various aspects of your application. Performance fundamentals Performance means efficiency. In the context of Open Web Apps, this document explains in general what performance is, how the browser platform helps improve it, and what tools and processes you can use to test and improve it. Populating the page: how browsers work Users want web experiences with content that is fast to load and smooth to interact with. Therefore, a developer should strive to achieve these two goals. To understand how to improve performance and perceived performance, it helps to understand how the browser works. Understanding latency Latency is the time it takes for a packet of data to travel from source to a destination. In terms of performance optimization, it's important to optimize to reduce causes of latency and to test site performance emulating high latency to optimize for users with slow or unreliable connections. Recommended Web Performance Timings: How long is too long? There are no clear set rules as to what constitutes a slow pace when loading pages, but there are specific guidelines for indicating content will load (1 second), idling (50ms), animating (16.7ms) and responding to user input (50 to 200ms). Using dns-prefetch DNS-prefetch is an attempt to resolve domain names before resources get requested. This could be a file loaded later or link target a user tries to follow. Navigation and resource timings Navigation timings are metrics measuring a browser's document navigation events. Resource timings are detailed network timing measurements regarding the loading of an application's resources. Both provide the same read-only properties, but navigation timing measures the main document's timings whereas the resource timing provides the times for all the assets or resources called in by that main document and the resources' requested resources. Optimizing startup performance Improving your startup performance is often one of the highest value performance optimizations that can be made. Good user experience includes ensuring your app loads quickly. This article provides performance tips and suggestions for both writing new applications and porting applications to the web from other platforms. Critical rendering path The Critical Rendering Path is the sequence of steps the browser goes through to convert the HTML, CSS, and JavaScript into pixels on the screen. Optimizing the critical render path improves render performance. The critical rendering path includes the Document Object Model (DOM), CSS Object Model (CSSOM), render tree and layout. Lazy loading Lazy loading is a strategy to identify resources as non-blocking (non-critical) and load these only when needed. It's a way to shorten the length of the critical rendering path , which translates into reduced page load times. Speculative loading Speculative loading refers to the practice of performing navigation actions (such as DNS fetching, fetching resources, or rendering documents) before the associated pages are actually visited, based on predictions as to what pages the user is most likely to visit next. Performance budgets A performance budget is a limit to prevent regressions. It can apply to a file, a file type, all files loaded on a page, a specific metric (e.g., Time to Interactive ), a custom metric (e.g., Time to Hero Element), or a threshold over a period of time. Performance Monitoring: RUM vs. synthetic monitoring Synthetic monitoring and real user monitoring (RUM) are two approaches for monitoring and providing insight into web performance. RUM and synthetic monitoring provide for different views of performance and have benefits, good use cases and shortfalls. RUM is generally best suited for understanding long-term trends whereas synthetic monitoring is very well suited to regression testing and mitigating shorter-term performance issues during development. In this article we define and compare these two performance monitoring approaches. CSS and JavaScript animation performance Animations are critical for a pleasurable user experience on many applications. There are many ways to implement web animations, such as CSS transitions / animations or JavaScript-based animations (using requestAnimationFrame() ). In this article, we analyze the performance differences between CSS-based and JavaScript-based animation. Animation performance and frame rate Animation on the web can be done via SVG , JavaScript , including <canvas> and WebGL , CSS animation , <video> , animated GIFs and even animated PNGs and other image types. The performance cost of animating a CSS property can vary from one property to another, and animating expensive CSS properties can result in Jank as the browser struggles to hit a smooth frame rate . Tutorials for beginners The MDN Web Performance Learning Area contains modern, up-to-date tutorials covering Performance essentials. Start here if you are a newcomer to performance: The "why" of web performance This article discusses why web performance is important for accessibility, user experience and your business goals. What is web performance? You know web performance is important, but what factors affect web performance and how is it measured? This article introduces the components of performance, from web page loading and rendering, including how your content makes it into your users' browser to be viewed, to what groups of people we need to consider when thinking about performance. How do users perceive performance? More important than how fast your website is in milliseconds, is how fast your users perceive your site to be. These perceptions are impacted by actual page load time, idling, responsiveness to user interaction, and the smoothness of scrolling and other animations. In this article, we discuss the various loading metrics, animation, and responsiveness metrics, along with best practices to improve user perception, if not the actual timings. Measuring performance Now that you understand a few performance metrics, we take a deeper dive into performance tools, metrics, and APIs and how we can make performance part of the web development workflow. Multimedia: images The lowest hanging fruit of web performance is often media optimization. Serving different media files based on each user agent's capability, size, and pixel density is possible. In this article we discuss the impact images have on performance, and the methods to reduce the number of bytes sent per image. Multimedia: video The lowest hanging fruit of web performance is often media optimization. In this article we discuss the impact video content has on performance, and cover tips like removing audio tracks from background videos can improve performance. JavaScript performance optimization JavaScript, when used properly, can allow for interactive and immersive web experiences — or it can significantly harm download time, render time, in-app performance, battery life, and user experience. This article outlines some JavaScript best practices that should be considered to ensure even complex content is as performant as possible. HTML performance optimization Some attributes and the source order of your markup can impact the performance or your website. By minimizing the number of DOM nodes, making sure the best order and attributes are used for including content such as styles, scripts, media, and third-party scripts, you can drastically improve the user experience. This article looks in detail at how HTML can be used to ensure maximum performance. CSS performance optimization CSS may be a less important optimization focus for improved performance, but there are some CSS features that impact performance more than others. In this article we look at some CSS properties that impact performance and suggested ways of handling styles to ensure performance is not negatively impacted. The business case for web performance There are many things a developer can do to improve performance, but how fast is fast enough? How can you convince powers that be of the importance of these efforts? Once optimized, how can you ensure bloat doesn't come back? In this article we look at convincing management, developing a performance culture and performance budget, and introduce ways to ensure regressions don't sneak into your code base. Web Performance best practices & tips This article covers several topics at a basic level and provides links to deeper dives to improve performance for each topic. In addition to front-end topics such as HTML, CSS, JavaScript, and media files, it also covers APIs, developer tools, best practices, and bad practices relating to web performance. Performance APIs The Performance API is a group of standards used to measure the performance of web applications. The following pages provide overviews of the Performance APIs including information on how to use them: High precision timing The Performance API allows high precision measurements that are based on time in potential sub-millisecond resolution and a stable monotonic clock that is not subject to system clock skew or adjustments. The high resolution timers are needed for accurate benchmarking instead of the less precise and non-monotonic Date timestamps. Long animation frame timing Long animation frames (LoAFs) can impact the user experience of a website. They can cause slow user interface (UI) updates, resulting in seemingly unresponsive controls and janky (or non-smooth) animated effects and scrolling, leading to user frustration. The Long Animation Frames API allows developers to get information about the long animation frames and better understand their root causes. This article shows how to use the Long Animation Frames API. Monitoring bfcache blocking reasons The PerformanceNavigationTiming.notRestoredReasons property reports information on why the current document was blocked from using the bfcache on navigation. Developers can use this information to identify pages that need updates to make them bfcache-compatible, thereby improving site performance. Navigation timing Navigation Timing provides metrics associated with navigating from one page to another via the PerformanceNavigationTiming API. For example, you can determine how much time it takes to load or unload a document, or log the time it took until DOM construction has finished and interaction with the DOM is possible. Performance data The Performance API doesn't provide performance data analysis, or visualizations. However, the Performance API is integrated well with developer tools and its data is often sent to analytics end points and libraries to record performance metrics which help you to evaluate the data to find performance bottlenecks affecting your users. This page provides an overview about what sorts of Performance API data exists, how it is collected, and how it can be accessed. Resource Timing API Resource Timing enables retrieving and analyzing detailed network timing data for the loading of an application's resources. An application can use the timing metrics to determine, for example, the length of time it takes to load a specific resource (such as an image or a script) either implicitly as part of page load or explicitly from JavaScript, for example using the fetch() API. Server timing Server-Timing allows servers to communicate metrics about the request-response cycle to the user agent. You can collect this information and act on server-side metrics in the same way as all the other metrics processed with the Performance API. User Timing API Create application specific timestamps using the user timing API 's "mark" and "measure" entry types using high-precision timestamps that are part of the browser's performance timeline. Related APIs The following APIs are also useful for measuring and influencing page performance: Page Visibility API Provides events you can watch for to know when a document becomes visible or hidden, as well as features to look at the current visibility state of the page. Background Tasks API The Cooperative Scheduling of Background Tasks API (also referred to as the Background Tasks API or the requestIdleCallback() API) provides the ability to queue tasks to be executed automatically by the user agent when it determines that there is free time to do so. Beacon API The Beacon interface schedules an asynchronous and non-blocking request to a web server. Intersection Observer API The Intersection Observer API provides a way to asynchronously observe changes in the intersection of a target element with an ancestor element or with a top-level document's Viewport . This enabled use cases such as Timing element visibility to get asynchronously notified when elements of interest become visible. Media Capabilities API Exposes decoding and encoding abilities of a client device, such as whether media is supported and whether playback should be smooth and power efficient, with real time feedback about playback to better enable adaptive streaming, and access to display property information. Network Information API Information about the system's connection in terms of general connection type (e.g., 'wifi, 'cellular', etc.). This can be used to select high definition content or low definition content based on the user's connection. Battery Status API The Battery API , provides information about the system's battery charge level and lets you be notified by events that are sent when the battery level or charging status change. This can be used to adjust your app's resource usage to reduce battery drain when the battery is low, or to save changes before the battery runs out in order to prevent data loss. Navigator.deviceMemory The deviceMemory read-only property of the Navigator interface returns the approximate amount of device memory in gigabytes. FetchEvent.preloadResponse The preloadResponse read-only property of the FetchEvent interface returns a Promise that resolves to the navigation preload Response if navigation preload was triggered, or undefined otherwise. Profiling and tooling Firefox Profiler Performance Features This website provides information on how to use and understand the performance features in your developer tools, including Call Tree , Flame Graph , Stack Chart , Marker Chart and Network Chart . Profiling with the built-in profiler Learn how to profile app performance with Firefox's built-in profiler. References HTML <picture> element <video> element <source> element <img> attributes (like srcset ) for responsive images rel="preload" attribute for preloading content via HTML CSS will-change JavaScript DOMContentLoaded Garbage collection requestAnimationFrame HTTP Content-encoding Resource hints via dns-prefetch , preconnect , prefetch , and prerender HTTP/2 Client Hints See also Responsive images HTML guide Web Workers API , including Using Service Workers and Using Web Workers Offline and background operation Caching Client hints Glossary terms: Beacon Brotli compression Content Delivery Networks (CDN) Cumulative Layout Shifts (CLS) Code splitting CSSOM Domain sharding Effective connection type First contentful paint (FCP) First CPU idle First paint gzip_compression HTTP/2 HTTP Interaction to next paint (INP) Jank Largest Contentful Paint (LCP) Latency Lazy load Long task Lossless compression Lossy compression Main thread Minification Network throttling Packet Page load time Page prediction Parse Perceived performance Prefetch Prerender QUIC RAIL Real User Monitoring (RUM) Resource Timing Round Trip Time (RTT) Server Timing Speculative parsing Speed index (and Perceptual Speed Index) SSL Synthetic monitoring TCP handshake TCP slow start Transmission Control Protocol (TCP) Time to first byte (TTFB) Time to interactive (TTI) TLS Tree shaking Web performance Performance in Firefox Developer Tools Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 18, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Performance Guides Performance fundamentals How browsers work Understanding latency How long is too long? Using dns-prefetch Navigation and resource timings Optimizing startup performance Critical rendering path Lazy loading Speculative loading Performance budgets RUM vs. synthetic monitoring CSS and JavaScript animations Animations and frame rate Tutorials Learn web performance Overview Best practices & tips Measuring performance Multimedia: Images Multimedia: video Perceived performance Performance business case Performant CSS Performant HTML Performant JavaScript The "why" of web performance What is web performance? Reference Performance APIs Overview High precision timing Long animation frame timing Monitoring bfcache blocking reasons Experimental Navigation timing Performance data Resource timing Server timing User timing Related_APIs Beacon API Intersection Observer API Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/user-preferences#default-preferences | User Preferences - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences User Preferences Tenant Preferences Preference Evaluation Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Preferences User Preferences Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Preferences User Preferences OpenAI Open in ChatGPT Learn how user preferences work in SuprSend and how to capture them. OpenAI Open in ChatGPT Before you start: Make sure you’ve set up notification categories first. See Manage Categories and Preferences for step-by-step instructions. Preferences let users control which notifications they receive. Instead of an all-or-nothing approach, users can opt out of specific categories, choose preferred channels, and set notification frequency. This granular control reduces the chance that users disable all notifications from your platform. In SuprSend, you can use ready-made UI and APIs to manage multi-tenant preference use cases. This includes letting admins set preferences for internal teams and handle notifications for enterprise customers, where companies, customers, and end users have distinct preferences. How It Works Preferences are evaluated in priority order: User Preference → Tenant Default → Category Default Three Levels of Control Global channel opt-outs, category preferences, and channel opt-outs within categories What are user preferences? Preferences only work with sub-categories: User preferences apply to sub-categories you create, not root-categories (System, Transactional, Promotional). Use sub-category slugs in workflows for preferences to work. Each user has a preference set that controls which notifications they receive. A preference set has three levels of control: channel_preferences — Global channel opt-outs (e.g., opt out of all email) categories — Category-level preferences (opt in/out of all channels of a notification type) opt_out_channels — Opt-in/out of specific channels within a category Example: Copy Ask AI { "channel_preferences" : [ { "channel" : "email" , "is_restricted" : true } ], "categories" : [ { "category" : "invoice-ready" , "preference" : "opt_out" }, { "category" : "payment-reminder" , "preference" : "opt_in" , "opt_out_channels" : [ "slack" ] } ] } In this example: user opted out of email globally, opted out of invoice-ready category completely, and stays opted in to payment-reminder but without Slack. How preferences are determined When a user hasn’t set their own preferences in a category, SuprSend uses defaults in this order: User Preference — Individual user’s explicit choices (highest priority) Tenant Default Preference — Default preferences set by tenant for the category Category Default Preference — Default preferences set at the category level (lowest priority) Preference precedence: User Preference → Tenant Default Preference → Category Default Preference Preference precedence is determined at category level . So, if a user overrides preference for a category but doesn’t touch other categories, defaults continue to apply to the untouched categories. Setting up preference categories Before users can set their preferences, you must first create and configure preference categories. For step-by-step setup instructions, see Manage Categories and Preferences . Default preferences Default preferences determine how users receive notifications when they haven’t set their own preferences. Configure these at the sub-category level when setting up categories. What default preferences control Default preferences control: Channel or Category defaults : Which categories or channels will be turned on/off by default on users’ preference page. Mandatory channels : Which channel or category users cannot opt out of (shown as disabled on preference page) Visibility : Whether a category appears on the preference page Preference types On — Users receive this category's notifications by default Users will receive notifications in this category by default. You can configure Opt-in Channels to specify which channels are included in the default “On” state: All : All available channels are enabled by default Selected Channels only : Only specific channels you select are enabled by default (e.g., Email, Android Push, iOS Push, In-App Inbox, MS Teams, Slack) Off — Users must opt in to get notifications Users will not receive notifications unless they change the preference. Can't Unsubscribe — Users cannot opt out of mandatory channels in this category Prevents users from fully opting out of the category. When selected, you can configure: Mandatory Channels : Channels which can’t be opted out of by the user. Set to “All” or “Selected Channels”. Opt-in Channels : In case of “Selected” Mandatory Channels, you can configure the channels that will be opted in by default. Channels other than mandatory and opt-in will be skipped for sending notification unless user explicitly opts in to them. Even when a category is set to “Can’t Unsubscribe,” users can still control channel-level preferences if your channel-level settings allow it. This configuration gives you fine-grained control over which channels a user is opted into by default, letting you differentiate between must-deliver channels, default-on channels, and optional channels. Capturing user preferences Users can set their preferences through one of the following methods: Hosted preference page Once you publish preference categories, SuprSend automatically generates a dedicated unsubscription webpage for collecting user preferences . Users can set channel-specific preferences from the hosted page. If the link is included in an email, the hosted page will show and save email preferences. Include it in your templates using {{$hosted_preference_url}} . This page is currently hosted on a SuprSend domain, but you can reach out to [email protected] if you’d prefer it hosted on your own domain. Embed in your product You can embed the preference interface directly inside your product using SuprSend’s ready-made UI components. SDKs exist in the languages below. Update your product preference page link on the tenant page and render it in templates using {{$embedded_preference_url}} . Javascript React Angular Embeddable preference page Controlling what categories to show on UI It’s always a good practice to show only the categories that are relevant to the user. There are two ways to achieve this: Hide categories for tenant users In a multi-tenant setup, tenants or admins can control which categories their users see. Setting visible_to_subscriber: false in tenant preferences hides the category from tenant users’ preference pages. Hidden categories won’t send notifications to those users, even if they previously opted in. Filter categories with tags Use tags to show categories based on user roles, departments, or teams. Filter categories in the preference center using the tags query parameter. 1 Setting Preference tags Tags can be added to sections and sub-categories directly from Developers → Notification Categories in the SuprSend Console. When a tag is assigned at the section level, it automatically applies to all categories under that section—so filtering by a section tag also filters its child categories. 2 Filter Categories with Tags You can filter categories using the tags query parameter in the API. This can be a simple tag match (e.g. tags=tag1 ) or a more advanced filter using logical operators. Supported operators: Operator Operand Datatype Description Example exists boolean Returns categories where any tag is set tags={ "exists": true } not string Excludes categories that have the specified tag tags={ "not": "admin" } or array Returns categories that match any of the provided tags tags={ "or": ["sales", "marketing"] } and array Returns categories that match all provided tags tags={ "and": ["sales", "manager"] } You can combine these operators for nested filtering like tags={ "or": [{ "and": ["sales", "manager"] }, { "and": ["marketing", "associate"] }] } . If no tags are provided, the preference center returns all visible categories. For details on how tags work, see Tags . Translating preference categories in user’s locale Upload translation files for your category names and descriptions. See How to manage Category translations for details. Once uploaded, pass a locale parameter (e.g., es , fr , de ) when: Loading the embeddable preference center As a query parameter in the get user preference API . The hosted preference page picks the locale from user’s profile. On hosted preference page, Dynamic content (category names, descriptions) is translated using translation files you upload. Static content (CTA text, labels, buttons, etc.) is translated automatically using SuprSend’s built-in i18n support for commonly used languages. You can see the list of supported languages below. Supported languages Language Code English en Spanish es French fr German de Italian it Portuguese pt Catalan ca Russian ru Dutch nl Polish pl Japanese ja Vietnamese vi Language Code Indonesian id Korean ko Serbian sr Norwegian no Hebrew he Chinese zh Finnish fi Swedish sv Czech cs Lithuanian lt Arabic ar How preferences are evaluated SuprSend evaluates user preferences at send time. For every recipient, the system checks user-level preferences first, then tenant-level overrides, and finally category defaults. For detailed information on the evaluation process, see Preference Evaluation . Other ways to unsubcribe from notifications In addition to the preference center within SuprSend, communication channels provide their own opt-out options, which SuprSend manages internally. Email: Unsubscribe URL header Gmail requires an unsubscribe URL in email headers when sending bulk emails (5,000+ emails/day). Most email providers expect you to add your own unsubscription page or offer a basic all-or-nothing opt-out option. You can add {{$hosted_preference_url}} here to load the SuprSend hosted preference page from the email header. Inbox (In-App): Render preference page inside your Inbox Companies also give users the option to load preference settings inside their in-app Inbox or provide a link to redirect users to the Preference center in their product. Mobile Push: Preference Page in App settings For mobile push notifications, users typically manage their preferences through the app settings. The category you assign in your workflow is also sent as the push “category” (used by Android/iOS to group notifications). If you set preference categories, the system automatically reflects them in the user’s app settings, loading similar preference controls. SMS & Whatsapp: Reply `STOP` Users generally unsubscribe from Short Message Service (SMS) by replying “STOP.” SuprSend automatically marks the SMS channel as inactive in the user’s profile when it receives a STOP reply. For WhatsApp, opt-out behavior depends on the provider; where supported, users can reply STOP and SuprSend will mark the channel inactive. FAQ How do I set up a digest schedule? You can create sub-categories for different digest schedules or set the digest schedule in the user profile and pass a dynamic schedule in the workflow digest node. An option to set the digest schedule directly on your preference page will be available soon. I have a use case where a company has multiple departments/roles, and the admin will set preferences for users in these departments. You can manage this with tenant preferences. In the SuprSend system, each tenant represents an organization, and the administrator sets which categories to send to their internal team using the tenant preference API . What happens to existing user preference view if I change default preference setting? Changing the default preference for a category doesn’t affect users who have already made changes to that category. For categories where users haven’t made any changes, the preferences update according to the new default settings. I have multiple enterprise customers with various product offerings. Customers should only receive notifications for the products they have enabled, and the same should be visible on their preference page. How can I manage this in SuprSend? You can turn off categories for tenants from the tenant page on the SuprSend console. Turning off the preference for a category automatically removes it from the tenant preference APIs and UI view. To further apply this to the tenant’s users, set visible to subscriber to false in the default tenant preferences to hide the category from the tenant’s end users. Why don't I see the 'inbox' channel in my user preferences? The inbox channel preference is behind a feature flag and needs to be enabled for your account. If you don’t see the inbox channel in your user preferences, contact [email protected] to have the feature flag enabled for your workspace. Why do users still receive promotional notifications even after unsubscribing from all categories? Unsubscribing from top-level categories (System, Transactional, Promotional) is not supported . Preferences only work with sub-categories you create. If you’re sending notifications using a top-level category like "promotional" in your workflows, users cannot unsubscribe from those notifications through the preference center, even if they unsubscribe from all visible categories. Solution: Create sub-categories under the Promotional category (e.g., “Marketing”, “Newsletter”, “Product Updates”) and use those sub-category slugs in your workflows instead of the top-level category. This allows users to: See and control preferences for each notification type Opt out of specific sub-categories Have their preferences respected when you send notifications Best practice: Organize notifications into meaningful sub-categories rather than using top-level categories directly. This provides users with granular control and improves their experience. Can I use user preferences in workflow branching to control which notifications are sent? User preferences are not passed in the workflow payload, so you cannot directly access them in branch conditions or other workflow nodes. Workaround: If you need to use preference-based logic in workflows (e.g., to route notifications based on user preferences or combine multiple notification scenarios in a single workflow), you can: Store the same preference data as custom properties in the user profile Use those custom properties in branch conditions to route notifications Example use case: If you want to combine multiple notification scenarios (e.g., “New Comment”, “Reply on my comment”, “I am mentioned”) in a single workflow to avoid duplicate notifications, you can: Store user preferences for each scenario as custom properties (e.g., wants_new_comment_notifications: true , wants_mention_notifications: true ) Use branch conditions to check these properties and route notifications accordingly This allows you to have one workflow that handles all scenarios while respecting user preferences Alternative approach: Create separate workflows for each notification scenario with conditions in the Trigger node. Each workflow can use its own preference category, allowing users to control each scenario independently. How do I let users control both notification on/off and the time they want to be reminded (e.g., medicine reminders)? You can combine preference categories with dynamic digest schedules to achieve this: 1. Set up preference categories: Create a preference category (e.g., “medicine-reminders”) that users can opt in/out of using the preference APIs or preference center UI . 2. Store time preference as user property: When users select their preferred reminder time, store it as a custom property in their user profile. For example: Copy Ask AI user.set({ "medicineReminderTime" : { "frequency" : "daily" , "time" : "09:00" , "tz_selection" : "recipient" } }) 3. Use dynamic schedule in digest node: In your workflow’s digest node, configure it to use a dynamic schedule that references the user property (e.g., ."$recipient".medicineReminderTime ). The digest will only send if the user has opted in to the category, and it will send at their preferred time. Implementation flow: Client side (React Native) : Capture user’s time preference and call your backend API Server side (Supabase Edge Function) : Update both the user’s preference (opt in/out) via SuprSend preference API and store the time preference as a user property Workflow : Use preference category to control on/off, and dynamic schedule to control timing For detailed information, see Dynamic Schedule in the digest documentation. Related documentation Notification Categories - Setting up categories & defaults Manage Categories and Preferences - Complete guide to setting up and managing categories and preferences Tenant Preferences - Managing tenant-level preferences Preference Evaluation - How SuprSend evaluates preferences at runtime Was this page helpful? Yes No Suggest edits Raise issue Previous Tenant Preferences Learn how to manage preferences for your tenants and their users. Next ⌘ I x github linkedin youtube Powered by On this page What are user preferences? How preferences are determined Setting up preference categories Default preferences What default preferences control Preference types Capturing user preferences Hosted preference page Embed in your product Controlling what categories to show on UI Hide categories for tenant users Filter categories with tags Translating preference categories in user’s locale How preferences are evaluated Other ways to unsubcribe from notifications FAQ Related documentation | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/API/HTML_DOM_API | The HTML DOM API - Web APIs | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Web APIs The HTML DOM API Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 中文 (简体) The HTML DOM API Baseline Widely available * This feature is well established and works across many devices and browser versions. It’s been available across browsers since July 2015. * Some parts of this feature may have varying levels of support. Learn more See full compatibility Report feedback The HTML DOM API is made up of the interfaces that define the functionality of each of the elements in HTML , as well as any supporting types and interfaces they rely upon. The functional areas included in the HTML DOM API include: Access to and control of HTML elements via the DOM . Access to and manipulation of form data. Interacting with the contents of 2D images and the context of an HTML <canvas> , for example to draw on top of them. Management of media connected to the HTML media elements ( <audio> and <video> ). Dragging and dropping of content on webpages. Access to the browser navigation history Supporting and connective interfaces for other APIs such as Web Components , Web Storage , Web Workers , WebSocket , and Server-sent events . In this article HTML DOM concepts and usage HTML DOM target audience HTML DOM API interfaces Examples Specifications Browser compatibility See also HTML DOM concepts and usage In this article, we'll focus on the parts of the HTML DOM that involve engaging with HTML elements. Discussion of other areas, such as Drag and Drop , WebSockets , Web Storage , etc. can be found in the documentation for those APIs. Structure of an HTML document The Document Object Model ( DOM ) is an architecture that describes the structure of a document ; each document is represented by an instance of the interface Document . A document, in turn, consists of a hierarchical tree of nodes , in which a node is a fundamental record representing a single object within the document (such as an element or text node). Nodes may be strictly organizational, providing a means for grouping other nodes together or for providing a point at which a hierarchy can be constructed; other nodes may represent visible components of a document. Each node is based on the Node interface, which provides properties for getting information about the node as well as methods for creating, deleting, and organizing nodes within the DOM. Nodes don't have any concept of including the content that is actually displayed in the document. They're empty vessels. The fundamental notion of a node that can represent visual content is introduced by the Element interface. An Element object instance represents a single element in a document created using either HTML or an XML vocabulary such as SVG . For example, consider a document with two elements, one of which has two more elements nested inside it: While the Document interface is defined as part of the DOM specification, the HTML specification significantly enhances it to add information specific to using the DOM in the context of a web browser, as well as to using it to represent HTML documents specifically. Among the things added to Document by the HTML standard are: Support for accessing various information provided by the HTTP headers when loading the page, such as the location from which the document was loaded, cookies , modification date , referring site , and so forth. Access to lists of elements in the document's <head> block and body , as well as lists of the images , links , scripts , etc. contained in the document. Support for interacting with the user by examining focus and by executing commands on editable content . Event handlers for document events defined by the HTML standard to allow access to mouse and keyboard events, drag and drop , media control , and more. Event handlers for events that can be delivered to both elements and documents; these presently include only copy , cut , and paste actions. HTML element interfaces The Element interface has been further adapted to represent HTML elements specifically by introducing the HTMLElement interface, which all more specific HTML element classes inherit from. This expands the Element class to add HTML-specific general features to the element nodes. Properties added by HTMLElement include for example hidden and innerText . An HTML document is a DOM tree in which each of the nodes is an HTML element, represented by the HTMLElement interface. The HTMLElement class, in turn, implements Node , so every element is also a node (but not the other way around). This way, the structural features implemented by the Node interface are also available to HTML elements, allowing them to be nested within each other, created and deleted, moved around, and so forth. The HTMLElement interface is generic, however, providing only the functionality common to all HTML elements such as the element's ID, its coordinates, the HTML making up the element, information about scroll position, and so forth. In order to expand upon the functionality of the core HTMLElement interface to provide the features needed by a specific element, the HTMLElement class is subclassed to add the needed properties and methods. For example, the <canvas> element is represented by an object of type HTMLCanvasElement . HTMLCanvasElement augments the HTMLElement type by adding properties such as height and methods like getContext() to provide canvas-specific features. The overall inheritance for HTML element classes looks like this: As such, an element inherits the properties and methods of all of its ancestors. For example, consider an <a> element, which is represented in the DOM by an object of type HTMLAnchorElement . The element, then, includes the anchor-specific properties and methods described in that class's documentation, but also those defined by HTMLElement and Element , as well as from Node and, finally, EventTarget . Each level defines a key aspect of the utility of the element. From Node , the element inherits concepts surrounding the ability for the element to be contained by another element, and to contain other elements itself. Of special importance is what is gained by inheriting from EventTarget : the ability to receive and handle events such as mouse clicks, play and pause events, and so forth. There are elements that share commonalities and thus have an additional intermediary type. For example, the <audio> and <video> elements both present audiovisual media. The corresponding types, HTMLAudioElement and HTMLVideoElement , are both based upon the common type HTMLMediaElement , which in turn is based upon HTMLElement and so forth. HTMLMediaElement defines the methods and properties held in common between audio and video elements. These element-specific interfaces make up the majority of the HTML DOM API, and are the focus of this article. The DOM article provides a general introduction to the DOM and its concepts. HTML DOM target audience The features exposed by the HTML DOM are among the most commonly-used APIs in a web developer's toolkit. All but the most simple web applications will use some features of the HTML DOM. HTML DOM API interfaces The majority of the interfaces that comprise the HTML DOM API map almost one-to-one to individual HTML elements, or to a small group of elements with similar functionality. In addition, the HTML DOM API includes a few interfaces and types to support the HTML element interfaces. HTML element interfaces These interfaces represent specific HTML elements (or sets of related elements which have the same properties and methods associated with them). HTMLAnchorElement HTMLAreaElement HTMLAudioElement HTMLBaseElement HTMLBodyElement HTMLBRElement HTMLButtonElement HTMLCanvasElement HTMLDataElement HTMLDataListElement HTMLDetailsElement HTMLDialogElement HTMLDirectoryElement HTMLDivElement HTMLDListElement HTMLElement HTMLEmbedElement HTMLFieldSetElement HTMLFormElement HTMLHRElement HTMLHeadElement HTMLHeadingElement HTMLHtmlElement HTMLIFrameElement HTMLImageElement HTMLInputElement HTMLLabelElement HTMLLegendElement HTMLLIElement HTMLLinkElement HTMLMapElement HTMLMediaElement HTMLMenuElement HTMLMetaElement HTMLMeterElement HTMLModElement HTMLObjectElement HTMLOListElement HTMLOptGroupElement HTMLOptionElement HTMLOutputElement HTMLParagraphElement HTMLPictureElement HTMLPreElement HTMLProgressElement HTMLQuoteElement HTMLScriptElement HTMLSelectElement HTMLSlotElement HTMLSourceElement HTMLSpanElement HTMLStyleElement HTMLTableCaptionElement HTMLTableCellElement HTMLTableColElement HTMLTableElement HTMLTableRowElement HTMLTableSectionElement HTMLTemplateElement HTMLTextAreaElement HTMLTimeElement HTMLTitleElement HTMLTrackElement HTMLUListElement HTMLUnknownElement HTMLVideoElement Deprecated HTML Element Interfaces HTMLMarqueeElement Deprecated Obsolete HTML Element Interfaces HTMLFontElement Deprecated HTMLFrameElement Deprecated HTMLFrameSetElement Deprecated Web app and browser integration interfaces These interfaces offer access to the browser window and document that contain the HTML, as well as to the browser's state, available plugins (if any), and various configuration options. BarProp Navigator Window Deprecated web app and browser integration interfaces External Deprecated Obsolete web app and browser integration interfaces Plugin Deprecated PluginArray Deprecated Form support interfaces These interfaces provide structure and functionality required by the elements used to create and manage forms, including the <form> and <input> elements. FormDataEvent HTMLFormControlsCollection HTMLOptionsCollection RadioNodeList ValidityState Canvas and image interfaces These interfaces represent objects used by the Canvas API as well as the <img> element and <picture> elements. CanvasGradient CanvasPattern CanvasRenderingContext2D ImageBitmap ImageBitmapRenderingContext ImageData OffscreenCanvas OffscreenCanvasRenderingContext2D Path2D TextMetrics Media interfaces The media interfaces provide HTML access to the contents of the media elements: <audio> and <video> . AudioTrack AudioTrackList MediaError TextTrack TextTrackCue TextTrackCueList TextTrackList TimeRanges TrackEvent VideoTrack VideoTrackList Drag and drop interfaces These interfaces are used by the HTML Drag and Drop API to represent individual draggable (or dragged) items, groups of dragged or draggable items, and to handle the drag and drop process. DataTransfer DataTransferItem DataTransferItemList DragEvent Page history interfaces The History API interfaces let you access information about the browser's history, as well as to shift the browser's current tab forward and backward through that history. BeforeUnloadEvent HashChangeEvent History Location PageRevealEvent PageSwapEvent PageTransitionEvent PopStateEvent Web Components interfaces These interfaces are used by the Web Components API to create and manage the available custom elements . CustomElementRegistry Miscellaneous and supporting interfaces These supporting object types are used in a variety of ways in the HTML DOM API. In addition, PromiseRejectionEvent represents the event delivered when a JavaScript Promise is rejected. DOMStringList DOMStringMap ErrorEvent HTMLAllCollection MimeType MimeTypeArray PromiseRejectionEvent Interfaces belonging to other APIs Several interfaces are technically defined in the HTML specification while actually being part of other APIs. Web storage interfaces The Web Storage API provides the ability for websites to store data either temporarily or permanently on the user's device for later re-use. Storage StorageEvent Web Workers interfaces These interfaces are used by the Web Workers API both to establish the ability for workers to interact with an app and its content, but also to support messaging between windows or apps. BroadcastChannel DedicatedWorkerGlobalScope MessageChannel MessageEvent MessagePort SharedWorker SharedWorkerGlobalScope Worker WorkerGlobalScope WorkerLocation WorkerNavigator WebSocket interfaces These interfaces, defined by the HTML specification, are used by the WebSockets API . CloseEvent WebSocket Server-sent events interfaces The EventSource interface represents the source which sent or is sending server-sent events . EventSource Examples In this example, an <input> element's input event is monitored in order to update the state of a form's "submit" button based on whether or not a given field currently has a value. JavaScript js const nameField = document.getElementById("userName"); const sendButton = document.getElementById("sendButton"); sendButton.disabled = true; // [note: this is disabled since it causes this article to always load with this example focused and scrolled into view] // nameField.focus(); nameField.addEventListener("input", (event) => { const elem = event.target; const valid = elem.value.length !== 0; if (valid && sendButton.disabled) { sendButton.disabled = false; } else if (!valid && !sendButton.disabled) { sendButton.disabled = true; } }); This code uses the Document interface's getElementById() method to get the DOM object representing the <input> elements whose IDs are userName and sendButton . With these, we can access the properties and methods that provide information about and grant control over these elements. The HTMLInputElement object for the "Send" button's disabled property is set to true , which disables the "Send" button so it can't be clicked. In addition, the user name input field is made the active focus by calling the focus() method it inherits from HTMLElement . Then addEventListener() is called to add a handler for the input event to the user name input. This code looks at the length of the current value of the input; if it's zero, then the "Send" button is disabled if it's not already disabled. Otherwise, the code ensures that the button is enabled. With this in place, the "Send" button is always enabled whenever the user name input field has a value, and disabled when it's empty. HTML The HTML for the form looks like this: html <p>Please provide the information below. Items marked with "*" are required.</p> <form action="" method="get"> <p> <label for="userName" required>Your name:</label> <input type="text" id="userName" /> (*) </p> <p> <label for="userEmail">Email:</label> <input type="email" id="userEmail" /> </p> <input type="submit" value="Send" id="sendButton" /> </form> Result Specifications Specification HTML # htmlelement Browser compatibility Enable JavaScript to view this browser compatibility table. See also References HTML elements reference HTML attribute reference Document Object Model (DOM) reference Guides DOM scripting introduction Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Oct 13, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar The HTML DOM API Guides Using microtasks in JavaScript with queueMicrotask() In depth: Microtasks and the JavaScript runtime environment Interfaces BeforeUnloadEvent DOMStringMap ErrorEvent HashChangeEvent ImageData HTMLAnchorElement HTMLAreaElement HTMLAudioElement HTMLBaseElement HTMLBodyElement HTMLBRElement HTMLButtonElement HTMLCanvasElement HTMLDataElement HTMLDataListElement HTMLDialogElement HTMLDivElement HTMLDListElement HTMLDocument HTMLElement HTMLEmbedElement HTMLFieldSetElement HTMLFormControlsCollection HTMLFormElement HTMLFrameSetElement Deprecated HTMLHeadElement HTMLHeadingElement HTMLHRElement HTMLHtmlElement HTMLIFrameElement HTMLImageElement HTMLInputElement HTMLLabelElement HTMLLegendElement HTMLLIElement HTMLLinkElement HTMLMapElement HTMLMediaElement HTMLMenuElement HTMLMetaElement HTMLMeterElement HTMLModElement HTMLObjectElement HTMLOListElement HTMLOptGroupElement HTMLOptionElement HTMLOptionsCollection HTMLOutputElement HTMLParagraphElement HTMLPictureElement HTMLPreElement HTMLProgressElement HTMLQuoteElement HTMLScriptElement HTMLSelectElement HTMLSourceElement HTMLSpanElement HTMLStyleElement HTMLTableCaptionElement HTMLTableCellElement HTMLTableColElement HTMLTableElement HTMLTableRowElement HTMLTableSectionElement HTMLTextAreaElement HTMLTemplateElement HTMLTimeElement HTMLTitleElement HTMLTrackElement HTMLUListElement HTMLUnknownElement HTMLVideoElement History Location MessageChannel MessageEvent MessagePort Navigator PageRevealEvent PageSwapEvent PageTransitionEvent Plugin Deprecated PluginArray Deprecated PromiseRejectionEvent RadioNodeList TimeRanges UserActivation ValidityState Window WorkletGlobalScope Events Document: DOMContentLoaded Document: readystatechange Element: afterscriptexecute Non-standard Deprecated Element: auxclick Element: beforescriptexecute Non-standard Deprecated Element: blur Element: click Element: contextmenu Element: DOMActivate Deprecated Element: focus Element: select HTMLDialogElement: cancel HTMLDialogElement: close HTMLElement: input HTMLElement: beforetoggle HTMLElement: toggle HTMLFormElement: reset HTMLFormElement: submit HTMLInputElement: change HTMLInputElement: invalid HTMLMediaElement: abort HTMLMediaElement: canplay HTMLMediaElement: canplaythrough HTMLMediaElement: durationchange HTMLMediaElement: emptied HTMLMediaElement: error HTMLMediaElement: loadeddata HTMLMediaElement: loadedmetadata HTMLMediaElement: loadstart HTMLMediaElement: play HTMLMediaElement: playing HTMLMediaElement: progress HTMLMediaElement: seeked HTMLMediaElement: seeking HTMLMediaElement: stalled HTMLMediaElement: suspend HTMLMediaElement: timeupdate HTMLMediaElement: volumechange HTMLMediaElement: waiting Window: afterprint Window: beforeprint Window: beforeunload Window: hashchange Window: languagechange Window: load Window: message Window: offline Window: online Window: pagehide Window: pageshow Window: rejectionhandled Window: storage Window: unload Window: unhandledrejection Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/At-rules | CSS at-rules - CSS | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web CSS Reference At-rules Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 CSS at-rules At-rules are CSS statements that instruct CSS how to behave. They are used to group and structure style rules and other at-rules, declare style information not directly associated with selected content, and manage syntactic constructs such as imports and namespaces keyword mappings. They begin with an at-sign, @ (U+0040 COMMERCIAL AT), followed by an identifier. In this article Index of at-rules and at-rule descriptors Index of media features Specifications See also Index of at-rules and at-rule descriptors @charset @color-profile @container @counter-style additive-symbols fallback negative pad prefix range speak-as suffix symbols system @custom-media @document Non-standard Deprecated @font-face ascent-override descent-override font-display font-family font-feature-settings font-stretch font-style font-variation-settings font-weight line-gap-override size-adjust src unicode-range @font-feature-values font-display @font-palette-values base-palette font-family override-colors @function Experimental @import @keyframes @layer @media (see list of media features in the next section) @namespace @page page-orientation size @position-try @property inherits initial-value syntax @scope @starting-style @supports @view-transition Index of media features -moz-device-pixel-ratio -webkit-animation -webkit-device-pixel-ratio -webkit-transform-2d -webkit-transform-3d -webkit-transition any-hover any-pointer aspect-ratio color color-gamut color-index device-aspect-ratio device-height display-mode dynamic-range forced-colors grid height horizontal-viewport-segments hover inverted-colors monochrome orientation overflow-block overflow-inline pointer prefers-color-scheme prefers-contrast prefers-reduced-data prefers-reduced-motion prefers-reduced-transparency resolution scan scripting shape update vertical-viewport-segments video-dynamic-range width Specifications Specification CSS Syntax Module Level 3 See also CSS at-rule functions Nesting at-rules CSS syntax module CSS conditional rules module Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 2, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar CSS Guides Modules Anchor positioning Animations Backgrounds and borders Basic user interface Borders and box decorations Box alignment Box model Box sizing Cascading and inheritance Color adjustment Colors Compositing and blending Conditional rules Containment Counter styles CSSOM view Custom functions and mixins Custom highlight API Custom properties for cascading variables Display Easing functions Environment variables Filter effects Flexible box layout Font loading Fonts Fragmentation Generated content Grid layout Images Inline layout Lists and counters Logical properties and values Masking Media queries Motion path Multi-column layout Namespaces Nesting Overflow Overscroll behavior Paged media Positioned layout Properties and values API Pseudo-elements Round display Ruby layout Scoping Scroll anchoring Scroll snap Scroll-driven animations Scrollbars styling Selectors Shadow parts Shapes Syntax Table Text Text decoration Transforms Transitions Values and units View transitions Viewport Writing modes Anchor positioning Using anchor positioning Handling overflow Animations Animatable properties Using animations Backgrounds and borders Using multiple backgrounds Resizing background images Scaling SVG backgrounds Box alignment Overview In block layout In flexbox In grid layout In multi-column layout Box model Introduction Margin collapsing Box sizing Aspect ratios Cascade Introduction Inheritance Specificity Property value processing Shorthand properties Cascading variables Using custom properties Colors Applying color Color values Using relative colors Using color wisely Accessibility: Colors and luminance Accessibility: Color contrast Columns Basic concepts Styling columns Using multi-column layouts Spanning and balancing columns Handling overflow Handling content breaks Conditional rules Using feature queries Using container scroll-state queries Containment Container queries Using containment Using container size and style queries CSSOM view Coordinate systems (API) Viewport concepts Custom functions and mixins Using CSS custom functions Display Block and inline layout Flow layout Flow layout and overflow Flow layout and writing modes In flow and out of flow Layout and the containing block Formatting contexts Block formatting context Inline formatting context Using multi-keyword syntax Visual formatting model Environment variables Using environment variables Filter effects Using filter effects Flexbox Basic concepts Flexbox and other layouts Aligning flex items Ordering flex items Controlling flex item ratios Wrapping flex items Typical use cases Fonts OpenType features Variable fonts WOFF Grid Basic concepts Grid and other layouts Using line-based placement Grid template areas Using named grid lines Using auto-placement Aligning items Logical values and writing modes Grid layout and accessibility Common grid layouts Subgrid Masonry layout Experimental Images Using gradients Using object-view-box Styling replaced elements Implementing image sprites Lists and counters Using counters Indenting lists Logical properties Basic concepts For floating and positioning For margins, borders, and padding For sizing Masking Introduction Clipping Multiple masks Mask properties Media queries Using media queries For accessibility Testing Printing Nesting style rules Nesting at-rules Nesting and specificity Using nesting Overflow Creating carousels Positioning Stacking context Example 1 Example 2 Example 3 Stacking floating elements Understanding z-index Using z-index Stacking without z-index Scroll anchoring Overview Scroll-driven animations Scroll-driven animation timelines Scroll snap Basic concepts Using scroll snap events Selectors Selectors and combinators Selector structure Privacy and :visited Using :target Shapes Overview Box-value shapes Image-based shapes Using shape-outside Syntax Introduction Comments At-rules Error handling Text Wrapping and breaking text Handling whitespace Text decoration Text shadows Transforms Using transforms Transitions Using transitions Values and units Value definition syntax Numeric data types Textual data types Using math functions Using typed arithmetic Writing modes Introduction Vertical form controls How to Layout cookbook Media objects Column layouts Center an element Sticky footers Split navigation Breadcrumb navigation List group with badges Pagination Card Grid wrapper Contribute a recipe Cookbook template Tools Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator Reference Properties -moz-* -moz-float-edge Non-standard Deprecated -moz-force-broken-image-icon Non-standard Deprecated -moz-orient Non-standard -moz-user-focus Non-standard Deprecated -moz-user-input Non-standard Deprecated -webkit-* -webkit-border-before Non-standard -webkit-box-reflect Non-standard -webkit-mask-box-image Non-standard -webkit-mask-composite Non-standard -webkit-mask-position-x Non-standard -webkit-mask-position-y Non-standard -webkit-mask-repeat-x Non-standard -webkit-mask-repeat-y Non-standard -webkit-tap-highlight-color Non-standard -webkit-text-fill-color -webkit-text-security Non-standard -webkit-text-stroke -webkit-text-stroke-color -webkit-text-stroke-width -webkit-touch-callout Non-standard Custom properties (--*): CSS variables accent-color align-* align-content align-items align-self alignment-baseline all anchor-name anchor-scope animation-* animation animation-composition animation-delay animation-direction animation-duration animation-fill-mode animation-iteration-count animation-name animation-play-state animation-range animation-range-end animation-range-start animation-timeline animation-timing-function appearance aspect-ratio backdrop-filter backface-visibility background-* background background-attachment background-blend-mode background-clip background-color background-image background-origin background-position background-position-x background-position-y background-repeat background-size baseline-source block-size border-* border border-block border-block-color border-block-end border-block-end-color border-block-end-style border-block-end-width border-block-start border-block-start-color border-block-start-style border-block-start-width border-block-style border-block-width border-bottom border-bottom-color border-bottom-left-radius border-bottom-right-radius border-bottom-style border-bottom-width border-collapse border-color border-end-end-radius border-end-start-radius border-image border-image-outset border-image-repeat border-image-slice border-image-source border-image-width border-inline border-inline-color border-inline-end border-inline-end-color border-inline-end-style border-inline-end-width border-inline-start border-inline-start-color border-inline-start-style border-inline-start-width border-inline-style border-inline-width border-left border-left-color border-left-style border-left-width border-radius border-right border-right-color border-right-style border-right-width border-spacing border-start-end-radius border-start-start-radius border-style border-top border-top-color border-top-left-radius border-top-right-radius border-top-style border-top-width border-width bottom box-* box-align Non-standard Deprecated box-decoration-break box-direction Non-standard Deprecated box-flex Non-standard Deprecated box-flex-group Non-standard Deprecated box-lines Non-standard Deprecated box-ordinal-group Non-standard Deprecated box-orient Non-standard Deprecated box-pack Non-standard Deprecated box-shadow box-sizing break-* break-after break-before break-inside caption-side caret-* caret Experimental caret-animation Experimental caret-color caret-shape Experimental clear clip-* clip Deprecated clip-path clip-rule color-* color color-interpolation color-interpolation-filters color-scheme column-* column-count column-fill column-gap column-rule column-rule-color column-rule-style column-rule-width column-span column-width columns contain-* contain contain-intrinsic-block-size contain-intrinsic-height contain-intrinsic-inline-size contain-intrinsic-size contain-intrinsic-width container-* container container-name container-type content content-visibility corner-* corner-block-end-shape Experimental corner-block-start-shape Experimental corner-bottom-left-shape Experimental corner-bottom-right-shape Experimental corner-bottom-shape Experimental corner-end-end-shape Experimental corner-end-start-shape Experimental corner-inline-end-shape Experimental corner-inline-start-shape Experimental corner-left-shape Experimental corner-right-shape Experimental corner-shape Experimental corner-start-end-shape Experimental corner-start-start-shape Experimental corner-top-left-shape Experimental corner-top-right-shape Experimental corner-top-shape Experimental counter-* counter-increment counter-reset counter-set cursor cx cy d direction display dominant-baseline dynamic-range-limit empty-cells field-sizing fill-* fill fill-opacity fill-rule filter flex-* flex flex-basis flex-direction flex-flow flex-grow flex-shrink flex-wrap float flood-color flood-opacity font-* font font-family font-feature-settings font-kerning font-language-override font-optical-sizing font-palette font-size font-size-adjust font-smooth Non-standard font-stretch Deprecated font-style font-synthesis font-synthesis-position Experimental font-synthesis-small-caps font-synthesis-style font-synthesis-weight font-variant font-variant-alternates font-variant-caps font-variant-east-asian font-variant-emoji font-variant-ligatures font-variant-numeric font-variant-position font-variation-settings font-weight forced-color-adjust gap grid-* grid grid-area grid-auto-columns grid-auto-flow grid-auto-rows grid-column grid-column-end grid-column-start grid-row grid-row-end grid-row-start grid-template grid-template-areas grid-template-columns grid-template-rows hanging-punctuation height hyphenate-character hyphenate-limit-chars hyphens image-* image-orientation image-rendering image-resolution Experimental initial-letter inline-size inset-* inset inset-block inset-block-end inset-block-start inset-inline inset-inline-end inset-inline-start interactivity Experimental interest-* interest-delay Experimental interest-delay-end Experimental interest-delay-start Experimental interpolate-size Experimental isolation justify-* justify-content justify-items justify-self left letter-spacing lighting-color line-* line-break line-clamp line-height line-height-step Experimental list-* list-style list-style-image list-style-position list-style-type margin-* margin margin-block margin-block-end margin-block-start margin-bottom margin-inline margin-inline-end margin-inline-start margin-left margin-right margin-top margin-trim Experimental marker-* marker marker-end marker-mid marker-start mask-* mask mask-border mask-border-mode mask-border-outset mask-border-repeat mask-border-slice mask-border-source mask-border-width mask-clip mask-composite mask-image mask-mode mask-origin mask-position mask-repeat mask-size mask-type math-* math-depth math-shift math-style max-* max-block-size max-height max-inline-size max-width min-* min-block-size min-height min-inline-size min-width mix-blend-mode object-* object-fit object-position object-view-box Experimental offset-* offset offset-anchor offset-distance offset-path offset-position offset-rotate opacity order orphans outline-* outline outline-color outline-offset outline-style outline-width overflow-* overflow overflow-anchor overflow-block overflow-clip-margin overflow-inline overflow-wrap overflow-x overflow-y overlay Experimental overscroll-* overscroll-behavior overscroll-behavior-block overscroll-behavior-inline overscroll-behavior-x overscroll-behavior-y padding-* padding padding-block padding-block-end padding-block-start padding-bottom padding-inline padding-inline-end padding-inline-start padding-left padding-right padding-top page-* page page-break-after Deprecated page-break-before Deprecated page-break-inside Deprecated paint-order perspective perspective-origin place-* place-content place-items place-self pointer-events position-* position position-anchor position-area position-try position-try-fallbacks position-try-order position-visibility print-color-adjust quotes r reading-flow Experimental reading-order Experimental resize right rotate row-gap ruby-* ruby-align ruby-overhang ruby-position rx ry scale scroll-* scroll-behavior scroll-margin scroll-margin-block scroll-margin-block-end scroll-margin-block-start scroll-margin-bottom scroll-margin-inline scroll-margin-inline-end scroll-margin-inline-start scroll-margin-left scroll-margin-right scroll-margin-top scroll-marker-group Experimental scroll-padding scroll-padding-block scroll-padding-block-end scroll-padding-block-start scroll-padding-bottom scroll-padding-inline scroll-padding-inline-end scroll-padding-inline-start scroll-padding-left scroll-padding-right scroll-padding-top scroll-snap-align scroll-snap-stop scroll-snap-type scroll-target-group Experimental scroll-timeline scroll-timeline-axis scroll-timeline-name scrollbar-* scrollbar-color scrollbar-gutter scrollbar-width shape-* shape-image-threshold shape-margin shape-outside shape-rendering speak-as Experimental stop-color stop-opacity stroke-* stroke stroke-dasharray stroke-dashoffset stroke-linecap stroke-linejoin stroke-miterlimit stroke-opacity stroke-width tab-size table-layout text-* text-align text-align-last text-anchor text-autospace text-box text-box-edge text-box-trim text-combine-upright text-decoration text-decoration-color text-decoration-inset Experimental text-decoration-line text-decoration-skip Experimental text-decoration-skip-ink text-decoration-style text-decoration-thickness text-emphasis text-emphasis-color text-emphasis-position text-emphasis-style text-indent text-justify text-orientation text-overflow text-rendering text-shadow text-size-adjust Experimental text-spacing-trim Experimental text-transform text-underline-offset text-underline-position text-wrap text-wrap-mode text-wrap-style timeline-scope top touch-action transform-* transform transform-box transform-origin transform-style transition-* transition transition-behavior transition-delay transition-duration transition-property transition-timing-function translate unicode-bidi user-modify Non-standard Deprecated user-select vector-effect vertical-align view-* view-timeline view-timeline-axis view-timeline-inset view-timeline-name view-transition-class view-transition-name visibility white-space white-space-collapse widows width will-change word-break word-spacing writing-mode x y z-index zoom Selectors & nesting selector Attribute selectors Class selectors ID selectors Keyframe selectors Namespace separator Selector list Type selectors Universal selectors Combinators Child combinator Column combinator Experimental Descendant combinator Next-sibling combinator Subsequent-sibling combinator Pseudo-classes :-moz-* :-moz-broken Non-standard Deprecated :-moz-drag-over Non-standard :-moz-first-node Experimental Non-standard :-moz-handler-blocked Non-standard :-moz-handler-crashed Non-standard :-moz-handler-disabled Non-standard :-moz-last-node Experimental Non-standard :-moz-loading Non-standard :-moz-locale-dir(ltr) Non-standard :-moz-locale-dir(rtl) Non-standard :-moz-only-whitespace Non-standard :-moz-submit-invalid Non-standard :-moz-suppressed Non-standard :-moz-user-disabled Non-standard :-moz-window-inactive Non-standard :active-* :active :active-view-transition :active-view-transition-type() :any-link :autofill :blank Experimental :buffering :checked :current Experimental :default :defined :dir() :disabled :empty :enabled :first-* :first :first-child :first-of-type :focus-* :focus :focus-visible :focus-within :fullscreen :future :has-slotted :has() :heading Experimental :heading() Experimental :host :host-context() Deprecated :host() :hover :in-range :indeterminate :interest-source Experimental :interest-target Experimental :invalid :is() :lang() :last-child :last-of-type :left :link :local-link Experimental :modal :muted :not() :nth-* :nth-child() :nth-last-child() :nth-last-of-type() :nth-of-type() :only-child :only-of-type :open :optional :out-of-range :past :paused :picture-in-picture :placeholder-shown :playing :popover-open :read-only :read-write :required :right :root :scope :seeking :stalled :state() :target-* :target :target-after Experimental :target-before Experimental :target-current Experimental :user-invalid :user-valid :valid :visited :volume-locked :where() Pseudo-elements ::-moz-* ::-moz-color-swatch Non-standard ::-moz-focus-inner Non-standard Deprecated ::-moz-list-bullet Experimental Non-standard ::-moz-list-number Experimental Non-standard ::-moz-meter-bar Non-standard ::-moz-progress-bar Experimental Non-standard ::-moz-range-progress Non-standard ::-moz-range-thumb Non-standard ::-moz-range-track Non-standard ::-webkit-* ::-webkit-inner-spin-button Non-standard ::-webkit-meter-bar Non-standard Deprecated ::-webkit-meter-even-less-good-value Non-standard ::-webkit-meter-inner-element Non-standard ::-webkit-meter-optimum-value Non-standard ::-webkit-meter-suboptimum-value Non-standard ::-webkit-progress-bar Non-standard ::-webkit-progress-inner-element Non-standard ::-webkit-progress-value Non-standard ::-webkit-scrollbar Non-standard ::-webkit-search-cancel-button Non-standard ::-webkit-search-results-button Non-standard ::-webkit-slider-runnable-track Non-standard ::-webkit-slider-thumb Non-standard ::after ::backdrop ::before ::checkmark Experimental ::column Experimental ::cue ::details-content ::file-selector-button ::first-letter ::first-line ::grammar-error ::highlight() ::marker ::part() ::picker-icon Experimental ::picker() Experimental ::placeholder ::scroll-* ::scroll-button() Experimental ::scroll-marker Experimental ::scroll-marker-group Experimental ::selection ::slotted() ::spelling-error ::target-text ::view-* ::view-transition ::view-transition-group() ::view-transition-image-pair() ::view-transition-new() ::view-transition-old() At-rules @charset @color-profile @container @counter-style @custom-media Experimental @document Non-standard Deprecated @font-face @font-feature-values @font-palette-values @function Experimental @import @keyframes @layer @media @namespace @page @position-try @property @scope @starting-style @supports @view-transition Values !important fit-content inherit initial max-content min-content revert revert-layer rule-list unset Types <absolute-size> <alpha-value> <angle-percentage> <angle> <axis> <baseline-position> <basic-shape> <blend-mode> <box-edge> <calc-keyword> <calc-sum> <color-interpolation-method> <color> <content-distribution> <content-position> <corner-shape-value> Experimental <custom-ident> <dashed-function> Experimental <dashed-ident> <dimension> <display-box> <display-inside> <display-internal> <display-legacy> <display-listitem> <display-outside> <easing-function> <filter-function> <flex> <frequency-percentage> <frequency> <generic-family> <gradient> <hex-color> <hue-interpolation-method> <hue> <ident> <image> <integer> <length-percentage> <length> <line-style> <named-color> <number> <overflow-position> <overflow> <percentage> <position-area> <position> <ratio> <relative-size> <resolution> <self-position> <shape> Deprecated <string> <system-color> <text-edge> <time-percentage> <time> <timeline-range-name> <transform-function> <url> Functions -moz-image-rect Non-standard Deprecated abs() acos() anchor-size() anchor() asin() atan() atan2() attr() blur() brightness() calc-size() Experimental calc() circle() clamp() color-mix() color() conic-gradient() contrast-color() contrast() cos() counter() counters() cross-fade() cubic-bezier() device-cmyk() drop-shadow() dynamic-range-limit-mix() Experimental element() Experimental ellipse() env() exp() fit-content() grayscale() hsl() hue-rotate() hwb() hypot() if() Experimental image-set() image() inset() invert() lab() lch() light-dark() linear-gradient() linear() log() matrix() matrix3d() max() min() minmax() mod() oklab() oklch() opacity() paint() path() perspective() polygon() pow() progress() radial-gradient() ray() rect() rem() repeat() repeating-conic-gradient() repeating-linear-gradient() repeating-radial-gradient() rgb() rotate() rotate3d() rotateX() rotateY() rotateZ() round() saturate() scale() scale3d() scaleX() scaleY() scaleZ() sepia() shape() sibling-count() sibling-index() sign() sin() skew() skewX() skewY() sqrt() steps() superellipse() Experimental symbols() tan() translate() translate3d() translateX() translateY() translateZ() type() Experimental url() var() xywh() Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/react-sdk#suprsendprovider | SDK Integration - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK SuprSend Client SDK Authentication Javascript Android iOS React Native Flutter React SDK Integration WebPush Preferences Events and User methods InApp Feed Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation React SDK Integration Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog React SDK Integration OpenAI Open in ChatGPT SDK Integration to enable SuprSend features like Inbox, Preferences, and Webpush into React-based web applications. OpenAI Open in ChatGPT Installation We support 2 SDK’s for react based applications. @suprsend/react-core : This provides context providers and hooks to integrate SuprSend in to your application. If you want to use web-push, user methods, track events or implement your own UI for preferences and inbox by using provided methods, this library is better option. If you want to use any of inbuilt components for inbox or preferences then use @suprsend/react . @suprsend/react : This library is built on top of @suprsend/react-core , so all hooks, context providers and methods that are present in @suprsend/react-core library are also present in this, with addition to that drop-in components like Inbox, NotificationsFeed, Preferences etc are available which comes with UI to ease integration. npm yarn Copy Ask AI npm install @ suprsend / react Integration SuprSendProvider This context provider need to be wrapper around your component in which you want to use SuprSend methods. This is responsible for creating client instance( new SuprSend() ), identify and reset user. You can access the SuprSend client instance using useSuprSendClient hook. This instance contains all methods needed to integrate preferences, webpush, track events and user methods. Example.js TypeDef Copy Ask AI import { SuprSendProvider } from '@suprsend/react' ; function Example () { return ( < SuprSendProvider publicApiKey = { YOUR_KEY } distinctId = { YOUR_DISTINCT_ID } > < MyComponent /> </ SuprSendProvider > ); } Parameter Description publicApiKey public API Key is mandatory field without which error will be thrown by SuprSendProvider. You can get this from SuprSend Dashboard . distinctId Unique identifier to identify a user across platform. If a value is passed SDK will create user and authenticate user. If null value is passed authenticated user’s instance data will be cleared in your application, kind of logout. userToken Mandatory when enhanced security mode is on. This is ES256 JWT token generated in your server-side. Refer docs to create userToken. refreshUserToken This function is called by SDK internally to get new userToken before existing token is expired. The returned JWT token string is used as the new userToken. userAuthenticationHandler This callback will be called after authenticating user internally when you pass distinctId field to give you back the response of user creation API call. host Customise the host url. vapidKey This key is needed only if you are implementing WebPush notifications. You can get it in SuprSend Dashboard —> Vendors —> WebPush swFileName This key is needed only if you are implementing WebPush notifications and want to customise default serviceworker.js file name with your own service worker file name. After implementing the above SuprSendProvider you can be able to use all SuprSend features. useSuprSendClient This hook is used to access internal SuprSend client instance which has all methods related to webpush, preferences, user methods and track event. Use this hook inside child of SuprSendProvider. Example.js Copy Ask AI import { SuprSendProvider , useSuprSendClient } from "@suprsend/react" function Example () { return ( < SuprSendProvider publicApiKey = { YOUR_KEY } distinctId = { YOUR_DISTINCT_ID } > < MyComponent /> </ SuprSendProvider > ); } function MyComponent () { const suprSendClient = useSuprSendClient (); return ( < p onClick = { () => { // suprSendClient.track('testing'); // suprSendClient.user.setEmail(' [email protected] ') // suprSendClient.webpush.registerPush() // suprSendClient.user.preferences.getPreferences() } } > Click Me </ p > ); } useAuthenticateUser This hook is used to get authenticated user anywhere in your application inside SuprSendProvider. This can also be used to check if user is authenticated before calling any method of SuprSend. Example.js Copy Ask AI import { useAuthenticateUser } from '@suprsend/react' ; function MyComponent () { const { authenticatedUser } = useAuthenticateUser (); useEffect (() => { if ( authenticatedUser ) { console . log ( 'User is authenticated' , authenticatedUser ); } }, [ authenticatedUser ]); return < p > Hello world </ p > ; } Was this page helpful? Yes No Suggest edits Raise issue Previous WebPush Integration steps of webpush in react application. Next ⌘ I x github linkedin youtube Powered by On this page Installation Integration SuprSendProvider useSuprSendClient useAuthenticateUser | 2026-01-13T08:48:26 |
https://dev.to/t/githubactions | GitHub Actions - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close GitHub Actions Follow Hide GitHub Actions helps you automate, customize, and execute your software development workflows right in your repository. You can discover, create, and share actions to perform any job you'd like, including CI/CD, and combine actions in a completely customized workflow. Create Post about #githubactions Use this tag to share your experiences and insights with using GitHub Actions. Articles can focus on tips and tricks, real-world use cases, step-by-step tutorials, and best practices for authoring or using GitHub Actions in different contexts. 1️⃣ Get Started 2️⃣ Examples 3️⃣ Custom Actions Older #githubactions posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Making Retype Docs AI-Ready with llms.txt Automation zakaria chahboun zakaria chahboun zakaria chahboun Follow Jan 10 Making Retype Docs AI-Ready with llms.txt Automation # documentation # githubactions # markdown # devops Comments Add Comment 2 min read Building a Chrome Extension: From Idea to Automated Release Prajwol Shrestha Prajwol Shrestha Prajwol Shrestha Follow Jan 11 Building a Chrome Extension: From Idea to Automated Release # webdev # extensions # automation # githubactions Comments Add Comment 2 min read Bastion Host & GitHub Actions on Hostim.dev Pavel Pavel Pavel Follow Jan 8 Bastion Host & GitHub Actions on Hostim.dev # docker # githubactions # cicd # ci Comments Add Comment 2 min read Stop Manual Deploys: A 5-Minute Guide to GitHub Actions in 2026 Meena Nukala Meena Nukala Meena Nukala Follow Jan 7 Stop Manual Deploys: A 5-Minute Guide to GitHub Actions in 2026 # github # git # githubactions # guide Comments Add Comment 2 min read Docker is Overkill: Setting Up Lightweight CI/CD for Solo Devs Akshith Anand Akshith Anand Akshith Anand Follow Jan 4 Docker is Overkill: Setting Up Lightweight CI/CD for Solo Devs # webdev # cicd # githubactions # docker 1 reaction Comments Add Comment 7 min read Troubleshooting Auth Issues Pulling Multiple Images With BuildKit in Github Actions Joseph Yi Joseph Yi Joseph Yi Follow Jan 6 Troubleshooting Auth Issues Pulling Multiple Images With BuildKit in Github Actions # docker # githubactions # devops Comments Add Comment 2 min read 🚀 Terraform Day 27: Automating Infrastructure with GitHub Actions (CI/CD) Jeeva Jeeva Jeeva Follow Dec 31 '25 🚀 Terraform Day 27: Automating Infrastructure with GitHub Actions (CI/CD) # githubactions # cicd # devops # terraform Comments Add Comment 2 min read Como fazer o upload de imagens Docker para a Huawei Cloud usando o GitHub Actions Matheus Farias de Oliveira Matsumoto Matheus Farias de Oliveira Matsumoto Matheus Farias de Oliveira Matsumoto Follow Dec 30 '25 Como fazer o upload de imagens Docker para a Huawei Cloud usando o GitHub Actions # githubactions # docker # huaweicloud # terraform Comments Add Comment 6 min read PlatformIO on GitHub Actions with cache accelerate aKuad aKuad aKuad Follow Dec 30 '25 PlatformIO on GitHub Actions with cache accelerate # githubactions # iot Comments Add Comment 2 min read GitHub Actions로 Docker 이미지 자동 빌드 및 배포하기 - 완벽 가이드 dss99911 dss99911 dss99911 Follow Dec 31 '25 GitHub Actions로 Docker 이미지 자동 빌드 및 배포하기 - 완벽 가이드 # infra # devops # githubactions # docker Comments Add Comment 3 min read Day-21 GitHub Actions, CI Triggers, and Understanding Runners 🚀 Jayanth Dasari Jayanth Dasari Jayanth Dasari Follow Dec 30 '25 Day-21 GitHub Actions, CI Triggers, and Understanding Runners 🚀 # devops # githubactions # cicd # jenkins Comments Add Comment 2 min read CI/CD Explained for Beginners (Using GitHub Actions Terms) Raji Sherifdeen ayinla Raji Sherifdeen ayinla Raji Sherifdeen ayinla Follow Dec 30 '25 CI/CD Explained for Beginners (Using GitHub Actions Terms) # devops # github # githubactions # softwaredevelopment 1 reaction Comments Add Comment 3 min read Improved Dependency Submission for GitHub Actions Jesse Houwing Jesse Houwing Jesse Houwing Follow Dec 27 '25 Improved Dependency Submission for GitHub Actions # githubactions # github # supplychainsecurity # security Comments Add Comment 3 min read GitHub Actions: From Zero to Production(EP10)✌️ Vishwark Vishwark Vishwark Follow Dec 25 '25 GitHub Actions: From Zero to Production(EP10)✌️ # github # githubactions # cicd # gitlab Comments Add Comment 3 min read Hello World to GitHub Actions: Your First Automated Workflow Vishwajeet Kondi Vishwajeet Kondi Vishwajeet Kondi Follow Dec 25 '25 Hello World to GitHub Actions: Your First Automated Workflow # githubactions # cicd # automation # devops Comments Add Comment 7 min read GitHub Actions: From Zero to Production(EP6)🚀 Vishwark Vishwark Vishwark Follow Dec 25 '25 GitHub Actions: From Zero to Production(EP6)🚀 # github # githubactions # cicd # gitlab Comments Add Comment 3 min read GitHub Actions: From Zero to Production(EP7)🚀 Vishwark Vishwark Vishwark Follow Dec 25 '25 GitHub Actions: From Zero to Production(EP7)🚀 # github # githubactions # cicd # gitlab Comments Add Comment 3 min read GitHub Actions: From Zero to Production(EP1)🚀 Vishwark Vishwark Vishwark Follow Dec 25 '25 GitHub Actions: From Zero to Production(EP1)🚀 # githubactions # frontend # github # cicd Comments Add Comment 2 min read GitHub Actions: From Zero to Production(EP4)🚀 Vishwark Vishwark Vishwark Follow Dec 25 '25 GitHub Actions: From Zero to Production(EP4)🚀 # github # githubactions # cicd # frontend Comments Add Comment 3 min read GitHub Actions: From Zero to Production(EP5) Vishwark Vishwark Vishwark Follow Dec 25 '25 GitHub Actions: From Zero to Production(EP5) # github # githubactions # frontend # cicd Comments Add Comment 2 min read GitHub Actions: From Zero to Production(EP3)🚀 Vishwark Vishwark Vishwark Follow Dec 25 '25 GitHub Actions: From Zero to Production(EP3)🚀 # githubactions # github # frontend # cicd Comments Add Comment 2 min read GitHub Actions: From Zero to Production(EP2)🚀 Vishwark Vishwark Vishwark Follow Dec 25 '25 GitHub Actions: From Zero to Production(EP2)🚀 # github # githubactions # frontend # cicd Comments Add Comment 2 min read CI/CD Pipelines : Understand in 3 Minutes Hongster Hongster Hongster Follow Dec 25 '25 CI/CD Pipelines : Understand in 3 Minutes # cicdpipeline # automation # githubactions # abotwrotethis Comments Add Comment 3 min read Is CI/CD Stifling Innovation? Reclaiming Developer Velocity in 2026 Barecheck Team Barecheck Team Barecheck Team Follow Dec 24 '25 Is CI/CD Stifling Innovation? Reclaiming Developer Velocity in 2026 # cicd # devops # automation # githubactions Comments Add Comment 4 min read 🚀 Stop Killing Your Bundle Size Chintan prajapati Chintan prajapati Chintan prajapati Follow Dec 26 '25 🚀 Stop Killing Your Bundle Size # typescript # javascript # performance # githubactions 3 reactions Comments Add Comment 3 min read loading... trending guides/resources Terraform Drift Detection Powered by GitHub Actions 10 GitHub Repos Every Serious Prompt Writer Should Be Using Alternatives to GitHub Actions for self-hosted runners Advent of AI 2025 - Day 1: Getting Goose to Generate Daily Fortunes in CI Use Markdownlint for your documentation Automate Terraform Module Releases on the public registry using GitHub Actions Advent of AI 2025 - Day 6: Automating GitHub Issue Triage with Goose Automatic Preview Environments with SST and GitHub Actions Automate Your Astro Blog with GitHub Actions Agentic DevOps: I Let GitHub Copilot Run My Entire CI/CD Pipeline (And Lived to Tell the Tale) Building a Zero-Downtime CI/CD Pipeline: Blue-Green Deployments for 100K+ Daily Requests How to Query a Railway SQLite Database from GitHub Actions Deploying a React Vite App to Azure App Service Using Docker & GitHub Actions (with OIDC) 🚀 CI/CD for Dummies Automate Content Quality with VectorLint GitHub Action AWS Cloud Resume Challenge - my attempt Improved Dependency Submission for GitHub Actions Building a Chrome Extension: From Idea to Automated Release Boost Developer productivity and DBOps efficiency with AWS Aurora Cloning Building a GitHub Action for Recurring Project Items 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/security | Security - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Security Security Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Security Security OpenAI Open in ChatGPT Learn how SuprSend handles security- data encryption, access control, network policies, & compliance standards. OpenAI Open in ChatGPT At SuprSend, we prioritize the security and privacy of your data. Our comprehensive security measures and adherence to industry standards ensure that your information is protected at every level. Security Compliance Our security measures meet industry standards for data protection and security. SOC 2 Type II Compliance: SuprSend has passed independent audits that confirm our systems are secure, reliable, and handle your data with care, not just once, but continuously over time. GDPR Compliance: We support EU-data residency options and support GDPR’s right to erasure workflows, ensuring compliance with data privacy regulations. HIPAA Compliance: SuprSend strictly safeguards sensitive health information, aligning with U.S. healthcare data protection regulations. CPRA Compliance: This compliance, an amendment of the earlier California Consumer Privacy Act (CCPA), implies to California residents’ privacy rights to correct inaccurate personal information and to limit the use of sensitive personal information for their customer rights. SuprSend strictly adheres to the CPRA standardization. ISO 27001: This international standardization continually improves and maintains an Information Security Management System (ISMS). SuprSend, being ISO 27001 complaint, majorly prioritizes confidentiality, integrity, & availability of information through its risk management framework. Security Controls The Security controls below highlight high-level details about our steps to implement best practices, identify and mitigate risks, and continuously develop ways to improve. To learn about our full security controls, please look at security practices. Data Security Production Databases Access Restriction: Access to production databases is highly restricted, limited to authorized personnel only. Multi-factor Authentication: All Staff members with access to critical systems use secure login mechanisms, including multi-factor authentication. Third-Party Assessments: We have thorough third-party penetration tests and infrastructure audits regularly. Data Encryption: Customer data in production databases and critical endpoints are encrypted to protect against unauthorized access. Data Backups: Regular backups are performed to meet recovery objectives, and the integrity of these backups is periodically tested. Server Logs Retention Policy: Server logs are retained for a maximum of 6 months, after which they are securely and permanently deleted. Automatic Session Timeout for Risk Mitigation: Sessions for accounts using email and password authentication, including those with two-factor authentication, automatically expire after three days of user inactivity to mitigate risks. Network Security Transmission Confidentiality: We use HTTPS with TLS 1.2 & above encryption, to secure transmitted data. Data Protection in Testing: Customer data in non-production environments receives the same security standards as in production. Centralized Security Event Logging: Our infrastructure logs security-related actions across critical systems for auditing purposes. We are committed to continually improving our privacy and data protection practices in accordance with relevant regulations. For more details, please visit: Privacy Policy Data Processing Agreement Data Subprocessors If you identify a security issue or an area for improvement, please email us at [email protected] . We will work with you to understand and resolve the issue. Security concerns are our top priority, and we will address any reported issues promptly. Was this page helpful? Yes No Suggest edits Raise issue Previous SDK Overview SuprSend SDKs to integrate notifications into your server-side and client-side applications. Next ⌘ I x github linkedin youtube Powered by On this page Security Compliance Security Controls Data Security Network Security | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/API/Web_Animations_API/Using_the_Web_Animations_API | Using the Web Animations API - Web APIs | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Web APIs Web Animations API Using the Web Animations API Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 Português (do Brasil) Русский 中文 (简体) Using the Web Animations API The Web Animations API lets us construct animations and control their playback with JavaScript. This article will start you off in the right direction with fun demos and tutorials featuring Alice in Wonderland. In this article Meet the Web Animations API Writing CSS Animations with the Web Animations API Controlling playback with play(), pause(), reverse(), and updatePlaybackRate() Persisting animation styles Automatically removing filling animations Getting information out of animations Callbacks and promises Conclusion See also Meet the Web Animations API The Web Animations API opens the browser's animation engine to developers and manipulation by JavaScript. This API was designed to underlie implementations of both CSS Animations and CSS Transitions , and leaves the door open to future animation effects. It is one of the most performant ways to animate on the Web, letting the browser make its own internal optimizations without hacks, coercion, or Window.requestAnimationFrame() . With the Web Animations API, we can move interactive animations from stylesheets to JavaScript, separating presentation from behavior. We no longer need to rely on DOM-heavy techniques such as writing CSS properties and scoping classes onto elements to control playback direction. And unlike pure, declarative CSS, JavaScript also lets us dynamically set values from properties to durations. For building custom animation libraries and creating interactive animations, the Web Animations API might be the perfect tool for the job. Let's see what it can do! This page contains a suite of examples utilizing the Web Animations API , inspired by Alice in Wonderland . These examples are created by and shared at the courtesy of Rachel Nabors . The full suite of examples are available on CodePen; here we present the ones relevant for our docs. Writing CSS Animations with the Web Animations API One of the more familiar ways to approach learning the Web Animations API is to start with something most web developers have played with before: CSS Animations. CSS Animations have a familiar syntax that breaks down nicely for demonstration purposes. The CSS version Here's a tumbling animation written in CSS showing Alice falling down the rabbit hole that leads to Wonderland: <div class="wrapper"> <div id="tunnel"></div> <div id="alice"> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 400"> <path d="M110.1 2.7h8.9c3.4.4 6.7.8 10.1 1.3 9.8 1.5 17.8 6.4 24.5 13.7.4.5 1.9.6 2.5.3 6.8-4.4 13.9-8.2 21.9-9.9 1.3-.3 3.4-1.2 3.7 1.5.6 4.9 1.4 9.9 1.7 14.8.3 4.4.1 8.7.1 12.2 2.1 1.5 4.6 2.3 5.5 4 4.2 8.4 3.2 17.6 3.1 26.6 0 1.2-.4 3.3.1 3.6 10.3 4.9 20.7 9.6 31.1 14.4 2.5-4.9-2.3-16-15.8-14.4.6-.5 1.4-1.1 2.2-1.1 2.5.1 4.9.4 7.4.7 6 .8 10.9 3.7 14.6 8.4 1.2 1.5 1.6 4.2 1.1 6.1-.7 3.2-3.7 4-7.1 4.1 4.5 3.5 6.5 8.1 6.8 13.3.6 9.4-1.1 18.6-4.8 27.1-3.9 8.8-5.2 17.5-3.3 26.8.6 3.2 1.2 7 .2 9.9-2 6.2-7.8 8.6-13.4 10.9-3 1.2-7.4 1.2-6.3 6.3.8 3.7-.4 4 .2 4.5 5.8 5.8 11.8 11.5 17.6 17.3 1.7 1.7 3 3.8 4.3 5.5-1.1.4-1.8.7-2.4 1 7.5 5.8 14.9 11.6 22.4 17.4 4.3-4.3 8.6-9 13.3-13.2 8.1-7.3 16.7-14 24.5-21.7 3.3-3.3 4.9-8.2 7.4-12.3.3-.4 1.3-.9 1.6-.7 4.6 2.7 6.8 7.2 7.9 12.1 1.3 5.7 1.6 11.6 2.3 17.1 4.2-.2 8.8-.8 13.4-.4 2 .1 4.6 1.8 5.5 3.5 2.2 4.3 3.8 8.9 5.3 13.5 3.7 11.5 6.9 23.2 10.7 34.7 1.7 5.1 3.4 10.4 8.6 13.4.5.3.5 2.7 0 3.1-3.3 2.5-6.9 4.6-10.5 7 2 5.8 4.3 12.6 6.7 19.6.7-.8 1.4-1.6 2.1-2.3 1.9-1.9 3.5-1.6 4.2 1.2.7 3 1.3 6.2 1.5 9.3.3 7.3.4 14.6.6 21.9 0 .4.2.8.5 1.2 3.6 4.7 7.1 9.3 10.7 14 1.7 2.3 3 5.4 5.3 6.6 5.5 2.7 11.5 4.4 17.3 6.6v.7c-.4.3-.7.8-1.2 1-5.8 2.1-11.6 4.3-17.5 6.2-4.2 1.3-8.4 2-12.4-1.2-1.8-1.5-3.9-2.6-5.8-3.8 0 2.3.1 4.4-.1 6.4-.1.8-.7 2.2-1.2 2.2-2.6.2-5.3.1-7.9.1-1.1 0-2.7.3-3.2-.3-1-1.2-2.1-2.9-2.1-4.4-.1-5.2.1-10.4.3-15.6.1-1.8 1.5-3.9.9-5.4-1.7-4.3-4-8.4-6.1-12.5-2.4-4.6-6.4-9.1-1.2-14.3.3-.3.3-1.3 0-1.7-4.7-6.5-9.5-13.1-14.4-19.5-1.2-1.5-2.9-3.7-4.4-3.7-6.7.1-13.4.8-20.1 1.3-.7.1-1.6.2-1.9.6-7.1 9.1-14 18.3-21.1 27.4-1.3 1.7-2.9 3.4-4.3 5 1.7.6 3.3 1.1 4.8 1.7.6.2 1.3.5 1.6 1 .2.3-.1 1.1-.4 1.5-2 2.6-4.1 5.2-6.1 7.8-4.3 5.3-8.7 10.5-13 15.9-.8 1-1.5 2.4-1.6 3.6-.2 5.4-.1 10.7-.1 16.1 0 1.5-.7 3.6.1 4.5 2.4 3 5.3 5.5 7.9 8.2 1.6 1.7 3 3.5 4.6 5.5-2.6.2-4.5.3-6.4.4h-3.7c-4.8-1.4-9.8-2.5-14.5-4.3-3.5-1.4-7.8-2.5-8-7.7-.1-2.1-.2-4.3-.4-6.7-1 1.1-1.7 2.1-2.6 2.9-.3.3-1 .4-1.3.2-1.9-1.1-3.7-2.2-5.5-3.4-1.7-1.1-4.5-1.6-3.5-4.5 2.3-6.5 6.4-11.6 12.7-14.9.6-.3 1.3-.9 1.6-1.5 3.9-8.2 7.8-16.4 11.8-24.6.7-1.5.4-4.5 3.8-3.8.2.1 1.2-3.1 1.8-4.9-2.8 1.5-5 2.9-7.4 3.9-7.4 3-14.7 6.4-23.1 5.6-8.5-.7-16.2-3.4-23.2-8-9.9-6.7-14.2-17-17.5-27.9-.5-1.7-.5-5.1-3.5-1.6-.1.2-.4.2-.6.3-2.5 1.7-5.4 3-6 6.5-.4 2.3-1 4.6-1.5 7-2.9 13.2-4.2 26.4-2.5 39.9 1.7 13.1 9.2 21.3 21 26.3 2.4 1 4.9 1.9 7.5 2.9-2.1.9-3.9 1.9-5.8 2.3-10.2 2.5-20.5 4.9-30.8 7.1-1.9.4-4.9.7-5.9-.3-6.4-6.5-8.9-14.8-8.3-23.7.7-9.6 2.1-19.2 3.9-28.6 2.2-11.5 6.1-22.5 11.7-32.9.7-1.3 2-3.1 1.6-4.1-1.8-4.6-4.5-8.9-6.2-13.6-2-5.7-4.2-11.6-1.2-17.8.1-.1-.3-.5-.5-.8 7.6.7 12.8 5.3 17.7 10.2-1.3-8.5-2.6-17.2-3.9-25.8 0-.3-.2-.7-.4-.9-6.7-5.5-13.3-11.2-17-19.2-2.6-5.7-4.3-11.8-6.3-17.7-.6-1.6.2-3.4-2.2-4.8-5.9-3.5-10.3-8.6-10.3-16 0-1.8 1.2-5 2.2-5.1 8.3-1.2 16.4-.1 23.8 4.2 2.4 1.4 4.9 2.7 8.1 4.4-.4-8.8-.8-16.2-1.2-23.6-4.2.9-8.6.9-11.5-2-3.3-3.3-5.4-7.8-7.9-11.8-1.1-1.7-2-3.6-3.5-6.4-3.8 10.3-7.4 19.9-10.8 29.1-.3-.6-1.1-1.7-1.5-2.9-3.5-10-2.8-20.2-1.1-30.3 1.2-7.4 4.3-14.6 3.1-22.4-.2-1.1.2-2.3.3-3.4-22.1 17.6-38.8 38.4-42.9 67.4-4 28-2.8 54.8 13.5 79.1-36.3-13.8-53-48.6-58.3-84.1-3 8-15 16.3-22.4 16.6v-.2c2.1-2.9 11.1-10.6 7-30.2-1.3-10.7-4.1-21.2-5.1-31.9-1-10.9-1-21.9-.5-32.9.3-11.6 3.8-22.7 8.6-33.2 5.7-12.5 13.5-23.8 23-33.6 5.6-5.8 11.9-11 18.2-16.1 8.6-6.8 17.7-12.9 28.2-16.5 5.1-1.9 10.4-3 15.7-4.5zm96.4 221.9c-.4.9-1.2 2-1.1 3 .5 7.6 1.2 15.2 2 22.7.2 2.1 0 4.8 3.3 5.5 3.3.7 6.6 1.8 9.9 2.6.3.1.9-.1 1.1-.4 3.8-4.8 7.5-9.6 10.9-14-8.4-6.1-17.1-12.6-26.1-19.4zm-23.1-42.5v6.3c1.9-2 3.6-3.9 5.3-5.7-1.7-.2-3.5-.4-5.3-.6z" /> </svg> </div> </div> Notice that the background moves, Alice spins, and her color changes at an offset from her spinning. We're going to focus on just Alice for this tutorial. You can check the full source code by clicking "Play" on the code block. Here's the simplified CSS that controls Alice's animation: css #alice { animation: alice-tumbling infinite 3s linear; } @keyframes alice-tumbling { 0% { color: black; transform: rotate(0) translate3d(-50%, -50%, 0); } 30% { color: #431236; } 100% { color: black; transform: rotate(360deg) translate3d(-50%, -50%, 0); } } #tunnel { animation: tunnel-fly 1s linear infinite; } @keyframes tunnel-fly { 100% { transform: translate3d(0, -300px, 0); } } #alice { color: #431236; width: 25%; position: absolute; top: 50%; left: 50%; transform-origin: 0 0; transform: rotate(0) translate3d(-50%, -50%, 0); backface-visibility: hidden; will-change: transform, color; } path { fill: currentColor; } #tunnel { background: url("/shared-assets/images/examples/web-animations/bg-tunnel-border-left.svg") repeat-y, url("/shared-assets/images/examples/web-animations/bg-tunnel-border-right.svg") repeat-y 100% 100%, url("/shared-assets/images/examples/web-animations/bg-tunnel-specks.png"), #6c373f; margin: 0 auto; height: calc(100% + 300px); width: 60%; min-width: 400px; backface-visibility: hidden; will-change: transform; } .wrapper { position: relative; width: 100%; height: 100%; overflow: hidden; } body { background: black; } html, body { height: 100%; } This changes Alice's color and her transform's rotation over 3 seconds at a constant (linear) rate and loops infinitely. In the @keyframes block we can see that 30% of the way through each loop (about .9 seconds in), Alice's color changes from black to a deep burgundy then back again by the end of the loop. Moving it to JavaScript Now let's try creating the same animation with the Web Animations API. Representing keyframes The first thing we need is to create a Keyframe Object corresponding to our CSS @keyframes block: js const aliceTumbling = [ { transform: "rotate(0) translate3d(-50%, -50%, 0)", color: "black" }, { color: "#431236", offset: 0.3 }, { transform: "rotate(360deg) translate3d(-50%, -50%, 0)", color: "black" }, ]; Here we're using an array containing multiple objects. Each object represents a key from the original CSS. However, unlike CSS, the Web Animations API doesn't need to explicitly be told the percentages along the animation for each key to appear at. It will automatically divide the animation into equal parts based on the number of keys you give it. This means that a Keyframe object with three keys will play the middle key 50% of the way through each loop of the animation unless told otherwise. When we want to explicitly set a key's offset from the other keys, we can specify an offset directly in the object, separated from the declaration with a comma. In the above example, to make sure that Alice's color changes at 30% (not 50%) for the color change, we are giving it offset: 0.3 . Currently, there should be at least two keyframes specified (representing the starting and ending states of the animation sequence). If your keyframe list has only one entry, Element.animate() may throw a NotSupportedError DOMException in some browsers until they are updated. So to recap, the keys are equally spaced by default unless you specify an offset on a key. Handy, no? Representing timing properties We'll also need to create an object of timing properties corresponding to the values in Alice's animation: js const aliceTiming = { duration: 3000, iterations: Infinity, }; You'll notice a few differences here from how equivalent values are represented in CSS: For one, the duration is in milliseconds as opposed to seconds — 3000 not 3s. Like setTimeout() and Window.requestAnimationFrame() , the Web Animations API only takes milliseconds. The other thing you'll notice is that it's iterations , not iteration-count . Note: There are a number of small differences between the terminology used in CSS Animations and the terminology used in Web Animations. For instance, Web Animations doesn't use the string "infinite" , but instead uses the JavaScript keyword Infinity . And instead of timing-function we use easing . We aren't listing an easing value here because, unlike CSS Animations where the default animation-timing-function is ease , in the Web Animations API the default easing is linear — which is what we want here. Bring the pieces together Now it's time to bring them both together with the Element.animate() method: js document.getElementById("alice").animate(aliceTumbling, aliceTiming); And boom: the animation starts playing: document .getElementById("tunnel") .animate( [ { transform: "translate3d(0, 0, 0)" }, { transform: "translate3d(0, -300px, 0)" }, ], { duration: 1000, iterations: Infinity, }, ); The animate() method can be called on any DOM element that could be animated with CSS. And it can be written in several ways. Instead of making objects for keyframes and timing properties, we could just pass their values in directly, like so: js document.getElementById("alice").animate( [ { transform: "rotate(0) translate3d(-50%, -50%, 0)", color: "black" }, { color: "#431236", offset: 0.3 }, { transform: "rotate(360deg) translate3d(-50%, -50%, 0)", color: "black" }, ], { duration: 3000, iterations: Infinity, }, ); What's more, if we only wanted to specify the duration of the animation and not its iterations (by default, animations iterate once), we could pass in the milliseconds alone: js document.getElementById("alice").animate( [ { transform: "rotate(0) translate3d(-50%, -50%, 0)", color: "black" }, { color: "#431236", offset: 0.3 }, { transform: "rotate(360deg) translate3d(-50%, -50%, 0)", color: "black" }, ], 3000, ); Controlling playback with play(), pause(), reverse(), and updatePlaybackRate() While we can write CSS Animations with the Web Animations API, where the API really comes in handy is manipulating the animation's playback. The Web Animations API provides several useful methods for controlling playback. Let's take a look at pausing and playing animations in the Follow the White Rabbit example: In this example, the white rabbit has an animation that causes it to go down a rabbit hole. It's only triggered when the user clicks on it. <div class="wrapper"> <div class="page"> <div class="background"></div> <div id="rabbit">Click the rabbit's ears!</div> <div class="foreground"></div> <p> She was just in time to see him pop down a hole between a great tree's roots. </p> </div> </div> #rabbit { background: url("/shared-assets/images/examples/web-animations/park5_rabbit.png") 0 0 / 100% 100%; cursor: pointer; position: absolute; top: 15%; left: 60%; width: 14.64844%; padding-top: 31.00586%; } body { background: black; } .wrapper { max-width: 133.33vh; margin: 0 auto; } .page { background: #431236; height: 0; overflow: hidden; padding-top: 75%; position: relative; text-indent: 100%; white-space: nowrap; } .foreground { height: 100%; background: url("/shared-assets/images/examples/web-animations/bg_park5_2.png") no-repeat 100% 100% / 100% auto; position: absolute; bottom: 0; left: 0; width: 100%; pointer-events: none; } .background { background: url("/shared-assets/images/examples/web-animations/bg_park5_1.png") no-repeat 0 0 / 100% auto; position: absolute; top: 0; left: 0; width: 100%; height: 100%; pointer-events: none; } Pausing and playing animations We can animate the rabbit using the animate() method as usual: js const whiteRabbit = document.getElementById("rabbit"); const rabbitDownAnimation = whiteRabbit.animate( [{ transform: "translateY(0%)" }, { transform: "translateY(100%)" }], { duration: 3000, fill: "forwards" }, ); The Element.animate() method will immediately run after it is called. To prevent the cake from eating itself up before the user has had the chance to click on it, we call Animation.pause() on it immediately after it is defined, like so: js rabbitDownAnimation.pause(); Note: Alternatively, you can define rabbitDownAnimation using the Animation() constructor instead, which doesn't start playing until you call play() . We can now use the Animation.play() method to run it whenever we're ready. Specifically, we want to link it to a clicking action. We can achieve this via the following: js whiteRabbit.addEventListener("click", downHeGoes); whiteRabbit.addEventListener("touchstart", downHeGoes); function downHeGoes(event) { whiteRabbit.removeEventListener("click", downHeGoes); whiteRabbit.removeEventListener("touchstart", downHeGoes); rabbitDownAnimation.play(); } When a user clicks or presses their finger on the rabbit, we can now call downHeGoes to make all the animations play. Other useful methods In addition to pausing and playing, we can use the following Animation methods: Animation.finish() skips to the end of the animation. Animation.cancel() aborts the animation and removes its effects. Animation.reverse() sets the animation's playback rate ( Animation.playbackRate ) to a negative value so it runs backward. Let's take a look at playbackRate first — a negative playbackRate will cause an animation to run in reverse. In Through the Looking-Glass , Alice travels to a world where she must run to stay in place — and run twice as fast to move forward! In the Red Queen's Race example, Alice and the Red Queen are running to stay in place: <div class="wrapper"> <div class="sky"></div> <div class="earth"> <div id="red-queen-and-alice"> <img id="red-queen-and-alice-sprite" src="/shared-assets/images/examples/web-animations/sprite_running-alice-queen_small.png" srcset=" /shared-assets/images/examples/web-animations/sprite_running-alice-queen.png 2x " alt="Alice and the Red Queen running to stay in place." /> </div> </div> <div class="scenery" id="foreground1"> <img id="palm3" src="/shared-assets/images/examples/web-animations/palm3_small.png" srcset="/shared-assets/images/examples/web-animations/palm3.png 2x" alt="" /> </div> <div class="scenery" id="foreground2"> <img id="bush" src="/shared-assets/images/examples/web-animations/bush_small.png" srcset="/shared-assets/images/examples/web-animations/bush.png 2x" alt="" /> <img id="w_rook_upright" src="/shared-assets/images/examples/web-animations/w_rook_upright_small.png" srcset=" /shared-assets/images/examples/web-animations/w_rook_upright.png 2x " alt="" /> </div> <div class="scenery" id="background1"> <img id="r_pawn_upright" src="/shared-assets/images/examples/web-animations/r_pawn_upright_small.png" srcset=" /shared-assets/images/examples/web-animations/r_pawn_upright.png 2x " alt="" /> <img id="w_rook" src="/shared-assets/images/examples/web-animations/w_rook_small.png" srcset="/shared-assets/images/examples/web-animations/w_rook.png 2x" alt="" /> <img id="palm1" src="/shared-assets/images/examples/web-animations/palm1_small.png" srcset="/shared-assets/images/examples/web-animations/palm1.png 2x" alt="" /> </div> <div class="scenery" id="background2"> <img id="r_pawn" src="/shared-assets/images/examples/web-animations/r_pawn_small.png" srcset="/shared-assets/images/examples/web-animations/r_pawn.png 2x" alt="" /> <img id="r_knight" src="/shared-assets/images/examples/web-animations/r_knight_small.png" srcset="/shared-assets/images/examples/web-animations/r_knight.png 2x" alt="" /> <img id="palm2" src="/shared-assets/images/examples/web-animations/palm2_small.png" srcset="/shared-assets/images/examples/web-animations/palm2.png 2x" alt="" /> </div> </div> * { user-select: none; } img { position: absolute; top: 50%; left: 50%; transform: translate(-50%, -50%); } .scenery { width: 100%; height: 50%; position: absolute; bottom: 0; left: 0; } #foreground1, #foreground2 { z-index: 1; } #foreground2, #background2 { transform: translateX(100%); } #palm3 { top: 0; left: 10%; } #w_rook_upright { top: 30%; left: 75%; } #r_pawn { top: 10%; left: 15%; } #w_rook { top: 10%; left: 80%; } #r_pawn_upright { top: 5%; left: 30%; } #r_knight { top: 0; left: 70%; } #palm2 { top: -15%; left: 90%; } #palm1 { top: -15%; left: 40%; } #bush { top: 55%; left: 20%; } #red-queen-and-alice { position: absolute; top: 0; left: 50%; transform: translate(-50%, -50%); overflow: hidden; width: 80%; max-width: 450px; z-index: 1; } #red-queen-and-alice::before { content: " "; display: block; padding-top: 87%; } #red-queen-and-alice img { position: absolute; top: 0; left: 0; width: 100%; } .sky, .earth { position: absolute; left: 0; height: 50vh; width: 100%; } .earth { background: #eb125d url("/shared-assets/images/examples/web-animations/bg_earth.jpg") repeat-x 0 0 / 100% auto; bottom: 0; } .sky { background: #246e89 url("/shared-assets/images/examples/web-animations/bg_sky.jpg") repeat-x 100% 100% / auto 100%; top: 0; } html, body { width: 100%; height: 100%; } .wrapper { width: 100%; height: 100%; overflow: hidden; position: relative; } const background1 = document.getElementById("background1"); const background2 = document.getElementById("background2"); const foreground1 = document.getElementById("foreground1"); const foreground2 = document.getElementById("foreground2"); const redQueenAliceSprite = document.getElementById( "red-queen-and-alice-sprite", ); /* Background animations */ const sceneryFrames = [ { transform: "translateX(100%)" }, { transform: "translateX(-100%)" }, ]; const sceneryTimingBackground = { duration: 36000, iterations: Infinity, }; const sceneryTimingForeground = { duration: 12000, iterations: Infinity, }; const background1Movement = background1.animate( sceneryFrames, sceneryTimingBackground, ); background1Movement.currentTime = background1Movement.effect.getComputedTiming().duration / 2; const background2Movement = background2.animate( sceneryFrames, sceneryTimingBackground, ); const foreground1Movement = foreground1.animate( sceneryFrames, sceneryTimingForeground, ); foreground1Movement.currentTime = foreground1Movement.effect.getComputedTiming().duration / 2; const foreground2Movement = foreground2.animate( sceneryFrames, sceneryTimingForeground, ); const spriteFrames = [ { transform: "translateY(0)" }, { transform: "translateY(-100%)" }, ]; const redQueenAlice = redQueenAliceSprite.animate(spriteFrames, { easing: "steps(7, end)", direction: "reverse", duration: 600, playbackRate: 1, iterations: Infinity, }); Because small children tire out easily, unlike automaton chess pieces, Alice is constantly slowing down. We can do this by setting a decay on her animation's playbackRate . We use updatePlaybackRate() instead of setting the playbackRate directly since that produces a smooth update: js setInterval(() => { // Make sure the playback rate never falls below .4 if (redQueenAlice.playbackRate > 0.4) { redQueenAlice.updatePlaybackRate(redQueenAlice.playbackRate * 0.9); } adjustBackgroundPlayback(); }, 1000); But urging them on by clicking or tapping causes them to speed up by multiplying their playbackRate : js function goFaster() { // But you can speed them up by giving the screen a click or a tap. redQueenAlice.updatePlaybackRate(redQueenAlice.playbackRate * 1.1); adjustBackgroundPlayback(); } document.addEventListener("click", goFaster); document.addEventListener("touchstart", goFaster); The background elements also have playbackRate s that are impacted when you click or tap. Their playback rates are derived from Alice's, shown below. What happens when you make Alice and the Red Queen run twice as fast? What happens when you let them slow down? js /* Alice tires so easily! Every so many seconds, reduce their playback rate so they slow a little. */ const sceneries = [ foreground1Movement, foreground2Movement, background1Movement, background2Movement, ]; function adjustBackgroundPlayback() { // If Alice and the Red Queen are running at a speed of 0.8–1.2, // the background doesn't move. // But if they fall under 0.8, the background slides backwards if (redQueenAlice.playbackRate < 0.8) { sceneries.forEach((anim) => { anim.updatePlaybackRate(-redQueenAlice.playbackRate / 2); }); } else if (redQueenAlice.playbackRate > 1.2) { sceneries.forEach((anim) => { anim.updatePlaybackRate(redQueenAlice.playbackRate / 2); }); } else { sceneries.forEach((anim) => { anim.updatePlaybackRate(0); }); } } adjustBackgroundPlayback(); Persisting animation styles When animating elements, a common use case is to persist the final state of the animation, after the animation has finished. One method sometimes used for this is to set the animation's fill mode to forwards . However, it is not recommended to use fill modes to persist the effect of an animation indefinitely, for two reasons: The browser has to maintain the state of the animation while it is still active, so the animation continues to consume resources even though it is no longer animating. Note that this is somewhat alleviated by the browser automatically removing filling animations . Styles applied by animations have a higher precedence in the cascade than specified styles, so it can be difficult to override them when needed. A better approach is to use the Animation.commitStyles() method. This writes the computed values of the animation's current styles into its target element's style attribute, after which the element can be restyled normally. Automatically removing filling animations It is possible to trigger a large number of animations on the same element. If they are indefinite (i.e., forwards-filling), this can result in a huge animations list, which could create a memory leak. For this reason, browsers automatically remove filling animations after they are replaced by newer animations, unless the developer explicitly specifies to keep them. Animations are removed when all of the following are true: The animation is filling (its fill is forwards if it is playing forwards, backwards if it is playing backwards, or both ). The animation is finished. (Note that because of the fill it will still be in effect.) The animation's timeline is monotonically increasing. (This is always true for DocumentTimeline ; other timelines such as scroll-timeline can run backwards.) The animation is not being controlled by declarative markup such as CSS. Every styling effect of the animation's AnimationEffect is being overridden by another animation that also satisfies all the conditions above. (Typically, when two animations would set the same style property of the same element, the one created last overrides the other.) The first four conditions ensure that, without intervention by JavaScript code, the animation's effect will never change or end. The last condition ensures that the animation will never actually affect the style of any element: it has been entirely replaced. When the animation is automatically removed, the animation's remove event fires. To prevent the browser from automatically removing animations, call the animation's persist() method. The animation's replaceState property will be removed if the animation has been removed, persisted if you have called persist() on the animation, or active otherwise. Getting information out of animations Imagine other ways we could use playbackRate, such as improving accessibility for users with vestibular disorders by letting them slow down animations across an entire site. That's impossible to do with CSS without recalculating durations in every CSS rule, but with the Web Animations API, we could use the Document.getAnimations method to loop over each animation on the page and halve their playbackRate s, like so: js document.getAnimations().forEach((animation) => { animation.updatePlaybackRate(animation.playbackRate * 0.5); }); With the Web Animations API, all you need to change is just one little property! Another thing that's tough to do with CSS Animations alone is creating dependencies on values provided by other animations. For instance, in the Growing and Shrinking Alice game example, you might have noticed something odd about the cake's duration: js document.getElementById("eat-me-sprite").animate([], { duration: aliceChange.effect.getComputedTiming().duration / 2, }); To understand what's happening here, let's take a look at Alice's animation: js const aliceChange = document .getElementById("alice") .animate( [ { transform: "translate(-50%, -50%) scale(.5)" }, { transform: "translate(-50%, -50%) scale(2)" }, ], { duration: 8000, easing: "ease-in-out", fill: "both", }, ); Alice's animation has her going from half her size to twice her size over 8 seconds. Then we pause her: js aliceChange.pause(); If we had left her paused at the beginning of her animation, she'd start at half her full size, as if she'd drunk the entire bottle already! We want to set her animation's "playhead" in the middle, so she's already halfway done. We could do that by setting her Animation.currentTime to 4 seconds, like so: js aliceChange.currentTime = 4000; But while working on this animation, we might change Alice's duration a lot. Wouldn't it be better if we set her currentTime dynamically, so we don't have to make two updates at a time? We can, in fact, do so by referencing aliceChange's Animation.effect property, which returns an object containing all the details of the effect(s) active on Alice: js aliceChange.currentTime = aliceChange.effect.getComputedTiming().duration / 2; effect lets us access the animation's keyframes and timing properties — aliceChange.effect.getComputedTiming() points to Alice's timing object — this contains her duration . We can divide her duration in half to get the midpoint for her animation's timeline, setting her to be normal height. Now we can reverse and play her animation in either direction to make her grow smaller or larger! And we can do the same thing when setting the cake and bottle durations: js const drinking = document .getElementById("liquid") .animate([{ height: "100%" }, { height: "0" }], { fill: "forwards", duration: aliceChange.effect.getComputedTiming().duration / 2, }); drinking.pause(); Now all three animations are linked to just one duration, which we can change easily from one place. We can also use the Web Animations API to figure out the animation's current time. The game ends when you run out of cake to eat or empty the bottle. Which vignette players are presented with depends on how far along Alice was in her animation, whether she grew too big and can't get in the tiny door anymore or too small and cannot reach the key to open the door. We can figure out whether she's on the large end or small end of her animation by getting her animation's currentTime and dividing it by her activeDuration : js const endGame = () => { // get Alice's timeline's playhead location const alicePlayhead = aliceChange.currentTime; const aliceTimeline = aliceChange.effect.getComputedTiming().activeDuration; // stops Alice's and other animations stopPlayingAlice(); // depending on which third it falls into const aliceHeight = alicePlayhead / aliceTimeline; if (aliceHeight <= 0.333) { // Alice got smaller! // … } else if (aliceHeight >= 0.666) { // Alice got bigger! // … } else { // Alice didn't change significantly // … } }; Callbacks and promises CSS Animations and Transitions have their own event listeners, and these are also possible with the Web Animations API: onfinish is the event handler for the finish event and can be triggered manually with finish() . oncancel is the event handler for the cancel event and can be triggers with cancel() . Here we set the callbacks for the cake, bottle, and Alice to fire the endGame function: js // When the cake or bottle runs out nommingCake.onfinish = endGame; drinking.onfinish = endGame; // Alice reaches the end of her animation aliceChange.onfinish = endGame; Better still, the Web Animations API also provides a finished promise that will resolve when the animation finishes, or reject if it is canceled. Conclusion These are the basic features of the Web Animations API. By now you should be ready to "jump down the rabbit hole" of animating in the browser and ready to write your own animation experiments! See also The full suite of Alice in Wonderland demos on CodePen for you to play with, fork, and share. Animating like you just don't care with Element.animate (2016) Explains the background of the Web Animations API and why it is more performant than other web animation methods. Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 7, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Web Animations API Guides Using the Web Animations API Web Animations API Concepts Keyframe Formats Web animation API tips and tricks Interfaces Animation AnimationEffect AnimationEvent AnimationTimeline AnimationPlaybackEvent DocumentTimeline KeyframeEffect ScrollTimeline ViewTimeline Properties Document .timeline Methods Document .getAnimations() Element .animate() Element .getAnimations() Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/JavaScript | JavaScript | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web JavaScript Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) JavaScript JavaScript ( JS ) is a lightweight interpreted (or just-in-time compiled ) programming language with first-class functions . While it is most well-known as the scripting language for Web pages, many non-browser environments also use it, such as Node.js , Apache CouchDB and Adobe Acrobat . JavaScript is a prototype-based , garbage-collected , dynamic language, supporting multiple paradigms such as imperative, functional, and object-oriented. JavaScript's dynamic capabilities include runtime object construction, variable parameter lists, function variables, dynamic script creation (via eval ), object introspection (via for...in and Object utilities ), and source-code recovery (JavaScript functions store their source text and can be retrieved through toString() ). This section is dedicated to the JavaScript language itself, and not the parts that are specific to Web pages or other host environments. For information about APIs that are specific to Web pages, please see Web APIs and DOM . The standards for JavaScript are the ECMAScript Language Specification (ECMA-262) and the ECMAScript Internationalization API specification (ECMA-402). As soon as one browser implements a feature, we try to document it. This means that cases where some proposals for new ECMAScript features have already been implemented in browsers, documentation and examples in MDN articles may use some of those new features. Most of the time, this happens between the stages 3 and 4, and is usually before the spec is officially published. Do not confuse JavaScript with the Java programming language — JavaScript is not "Interpreted Java" . Both "Java" and "JavaScript" are trademarks or registered trademarks of Oracle in the U.S. and other countries. However, the two programming languages have very different syntax, semantics, and use. JavaScript documentation of core language features (pure ECMAScript , for the most part) includes the following: The JavaScript guide The JavaScript reference For more information about JavaScript specifications and related technologies, see JavaScript technologies overview . In this article Beginner's tutorials JavaScript guides Reference Beginner's tutorials Our learn web development core modules contain modern, up-to-date tutorials covering JavaScript fundamentals. Your first website: Adding interactivity This article provides a brief tour of what JavaScript is and how to use it, aimed at people who are completely new to web development. Dynamic scripting with JavaScript This module focuses on the essentials of the core JavaScript language, plus some key surrounding topics — learning these topics will give you a solid basis to work from. JavaScript frameworks and libraries JavaScript frameworks are an essential part of modern front-end web development, providing developers with tried and tested tools for building scalable, interactive web applications. Many modern companies use frameworks as a standard part of their tooling, so many front-end development jobs now require framework experience. This set of articles provides a comfortable starting point to help you begin learning frameworks. JavaScript guides Fundamental language guides JavaScript Guide A much more detailed guide to the JavaScript language, aimed at those with previous programming experience either in JavaScript or another language. Intermediate Advanced JavaScript objects The object-oriented nature of JavaScript is important to understand if you want to go further with your knowledge of the language and write more efficient code, therefore we've provided this module to help you. Asynchronous JavaScript In this module, we take a look at asynchronous JavaScript, why it is important, and how it can be used to effectively handle potential blocking operations, such as fetching resources from a server. Client-side web APIs Explores what APIs are, and how to use some of the most common APIs you'll come across often in your development work. JavaScript language overview An overview of the basic syntax and semantics of JavaScript for those coming from other programming languages to get up to speed. JavaScript data structures Overview of available data structures in JavaScript. Equality comparisons and sameness JavaScript provides three different value comparison operations: strict equality using === , loose equality using == , and the Object.is() method. Enumerability and ownership of properties How different methods that visit a group of object properties one-by-one handle the enumerability and ownership of properties. Closures A closure is the combination of a function and the lexical environment within which that function was declared. Advanced Inheritance and the prototype chain Explanation of the widely misunderstood and underestimated prototype-based inheritance. Memory Management Memory life cycle and garbage collection in JavaScript. Reference Browse the complete JavaScript reference documentation. Standard objects Get to know standard built-in objects: Array , Boolean , Error , Function , JSON , Math , Number , Object , RegExp , String , Map , Set , WeakMap , WeakSet , and others. Expressions and operators Learn more about the behavior of JavaScript's operators instanceof , typeof , new , this , the operator precedence , and more. Statements and declarations Learn how do-while , for-in , for-of , try-catch , let , var , const , if-else , switch , and more JavaScript statements and keywords work. Functions Learn how to work with JavaScript's functions to develop your applications. Classes JavaScript classes are the most appropriate way to do object-oriented programming. Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Oct 2, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar JavaScript Tutorials and guides JavaScript Guide Introduction Grammar and types Control flow and error handling Loops and iteration Functions Expressions and operators Numbers and strings Representing dates & times Regular expressions Indexed collections Keyed collections Working with objects Using classes Using promises JavaScript typed arrays Iterators and generators Resource management Internationalization JavaScript modules Intermediate Language overview JavaScript data structures Equality comparisons and sameness Enumerability and ownership of properties Closures Advanced Inheritance and the prototype chain Meta programming Memory Management References Built-in objects AggregateError Array ArrayBuffer AsyncDisposableStack AsyncFunction AsyncGenerator AsyncGeneratorFunction AsyncIterator Atomics BigInt BigInt64Array BigUint64Array Boolean DataView Date decodeURI() decodeURIComponent() DisposableStack encodeURI() encodeURIComponent() Error escape() Deprecated eval() EvalError FinalizationRegistry Float16Array Float32Array Float64Array Function Generator GeneratorFunction globalThis Infinity Int8Array Int16Array Int32Array InternalError Non-standard Intl isFinite() isNaN() Iterator JSON Map Math NaN Number Object parseFloat() parseInt() Promise Proxy RangeError ReferenceError Reflect RegExp Set SharedArrayBuffer String SuppressedError Symbol SyntaxError Temporal TypedArray TypeError Uint8Array Uint8ClampedArray Uint16Array Uint32Array undefined unescape() Deprecated URIError WeakMap WeakRef WeakSet Expressions & operators Addition (+) Addition assignment (+=) Assignment (=) async function expression async function* expression await Bitwise AND (&) Bitwise AND assignment (&=) Bitwise NOT (~) Bitwise OR (|) Bitwise OR assignment (|=) Bitwise XOR (^) Bitwise XOR assignment (^=) class expression Comma operator (,) Conditional (ternary) operator Decrement (--) delete Destructuring Division (/) Division assignment (/=) Equality (==) Exponentiation (**) Exponentiation assignment (**=) function expression function* expression Greater than (>) Greater than or equal (>=) Grouping operator ( ) import.meta import.meta.resolve() import() in Increment (++) Inequality (!=) instanceof Left shift (<<) Left shift assignment (<<=) Less than (<) Less than or equal (<=) Logical AND (&&) Logical AND assignment (&&=) Logical NOT (!) Logical OR (||) Logical OR assignment (||=) Multiplication (*) Multiplication assignment (*=) new new.target null Nullish coalescing assignment (??=) Nullish coalescing operator (??) Object initializer Operator precedence Optional chaining (?.) Property accessors Remainder (%) Remainder assignment (%=) Right shift (>>) Right shift assignment (>>=) Spread syntax (...) Strict equality (===) Strict inequality (!==) Subtraction (-) Subtraction assignment (-=) super this typeof Unary negation (-) Unary plus (+) Unsigned right shift (>>>) Unsigned right shift assignment (>>>=) void operator yield yield* Statements & declarations async function async function* await using Block statement break class const continue debugger do...while Empty statement export Expression statement for for await...of for...in for...of function function* if...else import Import attributes Labeled statement let return switch throw try...catch using var while with Deprecated Functions Arrow function expressions Default parameters get Method definitions Rest parameters set The arguments object [Symbol.iterator]() callee Deprecated length Classes constructor extends Private elements Public class fields static Static initialization blocks Regular expressions Backreference: \1, \2 Capturing group: (...) Character class escape: \d, \D, \w, \W, \s, \S Character class: [...], [^...] Character escape: \n, \u{...} Disjunction: | Input boundary assertion: ^, $ Literal character: a, b Lookahead assertion: (?=...), (?!...) Lookbehind assertion: (?<=...), (?<!...) Modifier: (?ims-ims:...) Named backreference: \k<name> Named capturing group: (?<name>...) Non-capturing group: (?:...) Quantifier: *, +, ?, {n}, {n,}, {n,m} Unicode character class escape: \p{...}, \P{...} Wildcard: . Word boundary assertion: \b, \B Errors AggregateError: No Promise in Promise.any was resolved Error: Permission denied to access property "x" InternalError: too much recursion RangeError: argument is not a valid code point RangeError: BigInt division by zero RangeError: BigInt negative exponent RangeError: form must be one of 'NFC', 'NFD', 'NFKC', or 'NFKD' RangeError: invalid array length RangeError: invalid date RangeError: precision is out of range RangeError: radix must be an integer RangeError: repeat count must be less than infinity RangeError: repeat count must be non-negative RangeError: x can't be converted to BigInt because it isn't an integer ReferenceError: "x" is not defined ReferenceError: assignment to undeclared variable "x" ReferenceError: can't access lexical declaration 'X' before initialization ReferenceError: must call super constructor before using 'this' in derived class constructor ReferenceError: super() called twice in derived class constructor SyntaxError: 'arguments'/'eval' can't be defined or assigned to in strict mode code SyntaxError: "0"-prefixed octal literals are deprecated SyntaxError: "use strict" not allowed in function with non-simple parameters SyntaxError: "x" is a reserved identifier SyntaxError: \ at end of pattern SyntaxError: a declaration in the head of a for-of loop can't have an initializer SyntaxError: applying the 'delete' operator to an unqualified name is deprecated SyntaxError: arguments is not valid in fields SyntaxError: await is only valid in async functions, async generators and modules SyntaxError: await/yield expression can't be used in parameter SyntaxError: cannot use `??` unparenthesized within `||` and `&&` expressions SyntaxError: character class escape cannot be used in class range in regular expression SyntaxError: continue must be inside loop SyntaxError: duplicate capture group name in regular expression SyntaxError: duplicate formal argument x SyntaxError: for-in loop head declarations may not have initializers SyntaxError: function statement requires a name SyntaxError: functions cannot be labelled SyntaxError: getter and setter for private name #x should either be both static or non-static SyntaxError: getter functions must have no arguments SyntaxError: identifier starts immediately after numeric literal SyntaxError: illegal character SyntaxError: import declarations may only appear at top level of a module SyntaxError: incomplete quantifier in regular expression SyntaxError: invalid assignment left-hand side SyntaxError: invalid BigInt syntax SyntaxError: invalid capture group name in regular expression SyntaxError: invalid character in class in regular expression SyntaxError: invalid class set operation in regular expression SyntaxError: invalid decimal escape in regular expression SyntaxError: invalid identity escape in regular expression SyntaxError: invalid named capture reference in regular expression SyntaxError: invalid property name in regular expression SyntaxError: invalid range in character class SyntaxError: invalid regexp group SyntaxError: invalid regular expression flag "x" SyntaxError: invalid unicode escape in regular expression SyntaxError: JSON.parse: bad parsing SyntaxError: label not found SyntaxError: missing : after property id SyntaxError: missing ) after argument list SyntaxError: missing ) after condition SyntaxError: missing ] after element list SyntaxError: missing } after function body SyntaxError: missing } after property list SyntaxError: missing = in const declaration SyntaxError: missing formal parameter SyntaxError: missing name after . operator SyntaxError: missing variable name SyntaxError: negated character class with strings in regular expression SyntaxError: new keyword cannot be used with an optional chain SyntaxError: nothing to repeat SyntaxError: numbers out of order in {} quantifier. SyntaxError: octal escape sequences can't be used in untagged template literals or in strict mode code SyntaxError: parameter after rest parameter SyntaxError: private fields can't be deleted SyntaxError: property name __proto__ appears more than once in object literal SyntaxError: raw bracket is not allowed in regular expression with unicode flag SyntaxError: redeclaration of formal parameter "x" SyntaxError: reference to undeclared private field or method #x SyntaxError: rest parameter may not have a default SyntaxError: return not in function SyntaxError: setter functions must have one argument SyntaxError: string literal contains an unescaped line break SyntaxError: super() is only valid in derived class constructors SyntaxError: tagged template cannot be used with optional chain SyntaxError: Unexpected '#' used outside of class body SyntaxError: Unexpected token SyntaxError: unlabeled break must be inside loop or switch SyntaxError: unparenthesized unary expression can't appear on the left-hand side of '**' SyntaxError: use of super property/member accesses only valid within methods or eval code within methods SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed TypeError: 'x' is not iterable TypeError: "x" is (not) "y" TypeError: "x" is not a constructor TypeError: "x" is not a function TypeError: "x" is not a non-null object TypeError: "x" is read-only TypeError: already executing generator TypeError: BigInt value can't be serialized in JSON TypeError: calling a builtin X constructor without new is forbidden TypeError: can't access/set private field or method: object is not the right class TypeError: can't assign to property "x" on "y": not an object TypeError: can't convert BigInt to number TypeError: can't convert x to BigInt TypeError: can't define property "x": "obj" is not extensible TypeError: can't delete non-configurable array element TypeError: can't redefine non-configurable property "x" TypeError: can't set prototype of this object TypeError: can't set prototype: it would cause a prototype chain cycle TypeError: cannot use 'in' operator to search for 'x' in 'y' TypeError: class constructors must be invoked with 'new' TypeError: cyclic object value TypeError: derived class constructor returned invalid value x TypeError: getting private setter-only property TypeError: Initializing an object twice is an error with private fields/methods TypeError: invalid 'instanceof' operand 'x' TypeError: invalid Array.prototype.sort argument TypeError: invalid assignment to const "x" TypeError: Iterator/AsyncIterator constructor can't be used directly TypeError: matchAll/replaceAll must be called with a global RegExp TypeError: More arguments needed TypeError: null/undefined has no properties TypeError: property "x" is non-configurable and can't be deleted TypeError: Reduce of empty array with no initial value TypeError: setting getter-only property "x" TypeError: WeakSet key/WeakMap value 'x' must be an object or an unregistered symbol TypeError: X.prototype.y called on incompatible type URIError: malformed URI sequence Warning: -file- is being assigned a //# sourceMappingURL, but already has one Warning: unreachable code after return statement Misc JavaScript technologies overview Execution model Lexical grammar Iteration protocols Strict mode Template literals Trailing commas Deprecated features Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://www.fine.dev/blog/managing-technical-debt-in-startups | Managing Technical Debt: A Startup's Guide to Keeping Code Clean on a Tight Timeline Home Docs Changelog Pricing Sign in Get started -> Menu Home Docs Changelog Pricing <- Go Back Managing Technical Debt: A Startup's Guide to Keeping Code Clean on a Tight Timeline Technical debt is like the dust that collects under a couch: easy to ignore until it starts piling up, causing problems, and becoming a hassle to deal with. For early-stage startups, balancing the demands of delivering new features while managing technical debt is a constant tightrope walk. Often, the pressure to ship code quickly means compromises that can snowball into larger problems down the line. How can you keep your codebase clean without sacrificing speed? Let’s dive into some practical strategies. Table of Contents Define and Prioritize Debt Use AI Coding Agents to Help Minimize Technical Debt Leverage Automation to Identify Problems Early Refactor Regularly Educate and Empower Your Team Communicate with Stakeholders About the Trade-offs Measure and Celebrate Progress Conclusion 1. Define and Prioritize Debt Not all technical debt is created equal. Some debts are strategic – short-term trade-offs made to get a product out the door, with a plan for repayment later. Others are accidental, like poorly-written code resulting from unclear requirements. The first step to managing technical debt effectively is to categorize it. Once categorized, prioritize technical debt alongside other tasks. It’s often helpful to assign metrics to debt (e.g., code complexity or potential impact) to weigh it against feature development. By making technical debt part of the conversation at sprint planning, your team is less likely to accumulate crippling issues that endanger long-term scalability. *2. Use AI Coding Agents to Help Minimize Technical Debt** AI coding agents can be powerful allies in managing and reducing technical debt. These tools can help by automating code reviews, identifying areas in the codebase that need refactoring, and suggesting optimizations. For example, AI agents can analyze code complexity and highlight potential improvements that would otherwise go unnoticed. Using AI-powered platforms like Fine can help identify problematic patterns in real-time, recommend best practices, and even generate refactored code, freeing up developers to focus on higher-level tasks. By leveraging AI, teams can proactively manage technical debt rather than reacting to it after it accumulates. AI coding agents also assist in maintaining consistency in code quality, ensuring that new contributions adhere to established standards, which reduces the risk of technical debt building up over time. 3. Leverage Automation to Identify Problems Early Automated code reviews, linters, and static analysis tools are your allies in keeping technical debt in check. They help you catch issues like code duplication or unhandled edge cases that contribute to debt. Integrate these tools into your CI/CD pipeline to ensure that developers get real-time feedback. This helps reduce future debt while allowing you to focus on what matters: delivering value. Another angle is unit testing. It’s a foundational piece that helps ensure you’re not accruing debt each time a new feature is added. Automation doesn’t eliminate technical debt, but it does mean you’re dealing with it in smaller, manageable chunks rather than facing a mountain later on. 4. Refactor regularly Refactoring doesn’t have to be a major project done once a quarter. Instead, make it part of your development culture. Encourage your team to refactor a small portion of the codebase as they touch it for new features or bug fixes. The key here is consistency. Regularly reviewing and improving code ensures that you aren’t carrying forward suboptimal solutions. Incorporate time for refactoring into sprint cycles, even if it’s just a few hours per sprint. Over time, this can significantly reduce the amount of accumulated debt. The key for success when refactoring code regularly is having tests implemented across the codebase and a strong CI/CD sequence. You want to make sure that if something goes wrong, it's caught straight away and fixed. Using an AI tool such as [Fine]( https://ai.fine.dev ) enables you to quickly write tests for new and existing code. 4. Educate and Empower Your Team Building awareness around technical debt can transform how your team approaches code. Foster a culture where developers understand the consequences of debt and are encouraged to raise their hand when they see it piling up. This culture shift begins with education—hold workshops or discussions on the nature of technical debt, and share stories of teams who were derailed by an unmanaged backlog of issues. Empowerment also means providing your team with the right tools and authority to make decisions around debt repayment. Give your developers the autonomy to create tickets for issues they encounter, and back them up when they make the call that something needs fixing. 5. Communicate with Stakeholders About the Trade-offs Stakeholders often perceive technical debt as something intangible and secondary to new features. Bridging this understanding gap is crucial for garnering the support you need to manage debt effectively. The challenge is to translate technical debt into terms that resonate with the business: slower development velocity, increased bugs, and ultimately a diminished user experience. Practical examples of communicating technical debt to stakeholders include: Lost Revenue Due to Delays : Illustrate how technical debt can slow down the development of key features, which may cause missed market opportunities or delays in revenue-generating product launches. For example, "Because of the growing technical debt, adding the payment gateway feature will take an additional four weeks, delaying our ability to capture new customers." Increased Maintenance Costs : Show how technical debt leads to higher maintenance costs by requiring more resources to fix bugs or maintain the codebase. For instance, "Currently, our team is spending 30% more time fixing issues due to poorly structured code, reducing the time available for new feature development." Impact on User Satisfaction : Connect technical debt to user experience metrics. You could say, "Our app crashes are increasing due to unresolved technical debt, leading to a higher churn rate. Addressing these debts will improve stability and user satisfaction, reducing customer loss." Make the costs of inaction visible by tying technical debt to key metrics like team productivity or user satisfaction. Once stakeholders understand that managing technical debt prevents slowdowns and feature delays, they’ll be more willing to prioritize it. 6. Measure and Celebrate Progress Finally, tracking technical debt is important. You can measure the health of your codebase by tracking code quality metrics over time (e.g., maintainability index, complexity, or cyclomatic scores). Show these metrics to your team and celebrate when they improve—acknowledge that every step in reducing debt makes it easier for everyone to work. Reducing technical debt isn’t just about minimizing headaches for developers; it’s about creating a sustainable environment where the team can innovate, move fast, and avoid burnout. Celebrating even small wins reinforces the value of these efforts and keeps the team motivated to keep things clean. Conclusion Technical debt doesn’t have to be the monster under the bed. For startups, where speed is critical, managing technical debt effectively can be a game-changer for long-term growth. By integrating debt management into your regular processes, automating early detection, refactoring continuously, and communicating clearly with stakeholders, you can keep it at a manageable level. The goal isn’t to eliminate technical debt completely—it’s to ensure that it’s always understood, visible, and controllable. Balancing code cleanliness and tight timelines is especially challenging for startups that need to move fast and adapt. However, with the right mindset and tools, CTOs can steer their teams away from costly pitfalls and toward long-term success, all while maintaining a flexible and scalable codebase. Start building today Try out the smoothest way to build, launch and manage an app Try for Free -> © Fine.dev - All rights reserved. Product Overview AI Workflows Pricing & Plans Changelog Blog Docs Company Press Terms & Conditions Privacy policy | 2026-01-13T08:48:26 |
https://www.fine.dev/blog/integrating-ai-in-startup-tech-stack | The Best Practices for Integrating AI into Your Existing Startup Tech Stack Home Docs Changelog Pricing Sign in Get started -> Menu Home Docs Changelog Pricing <- Go Back The Best Practices for Integrating AI into Your Existing Startup Tech Stack Startups managed before AI and many are continuing just fine without seriously focusing on adoption. Many startups also rushed into wide adoption of AI tools and quickly found themselves paying for subscriptions and API keys which no one was uses. Worst of all, some adopted AI without realising the full implications for the quality of work. Here's how to approach choosing AI additions to your tech stack. Remember, not all AI SaaS is equal. Table of Contents 1. Start Small with a Specific Problem to Solve 2. Understand Your Data 3. Choose the Right AI Tools 4. Build for Scalability 5. Collaborate Across Teams 6. Leverage Existing Cloud Services 7. Train Your Team 8. Monitor and Optimize 9. Focus on Privacy and Compliance 10. Pilot Before Full Implementation 1. Start Small with a Specific Problem to Solve The first best practice for integrating AI is to start small. AI can do a lot, but trying to implement it all at once can lead to complications and inefficiencies. Instead, focus on a single issue that AI could solve, such as automating customer support, optimizing marketing efforts, or predicting sales trends. This targeted approach helps ensure that you experience success quickly, which can build internal support and excitement for AI adoption. Set a target for the use case - both application and solution. Set a deadline - we're going to try solving this problem with AI for 30 days. 2. Understand Your Data AI thrives on data, and the quality of the insights you derive depends heavily on the quality of the data you feed it. Assess your existing data—where it's coming from, how it's stored, and its overall quality. Clean, organized data is essential for effective AI integration. Take time to review your data pipelines and identify any gaps or areas where data needs to be cleaned or normalized. 3. Choose the Right AI Tools There are many AI tools available, ranging from pre-built solutions to customizable platforms. It's important to choose tools that align with your startup's current technology. Look for AI tools with APIs that integrate easily into your existing tech stack, whether you use cloud-based solutions, proprietary software, or other third-party services. Compatibility is key to avoiding costly and complex integration issues. Some tools have just added an OpenAI integration to their existing platform which doesn't really add much value, but it's trendy. Other new tools are just GPT-wrappers. Find tools that offer a concrete benefit to your business - time saved, improved customer satisfaction, improved DORA metrics, etc. 4. Build for Scalability When you are integrating AI, consider how your startup's needs might change as you grow. AI tools should be scalable, with the ability to handle increasing amounts of data and more complex tasks over time. Plan for the future by choosing AI solutions that can grow alongside your business, providing the flexibility you need for the long term. 5. Collaborate Across Teams AI integration shouldn't just be the responsibility of your engineering team. Cross-functional collaboration is essential. Marketing, operations, customer service, and other departments should all have input into how AI can best be leveraged in their respective areas. This collaborative approach not only ensures that your AI tools provide real value to each department but also increases adoption and minimizes resistance. 6. Leverage Existing Cloud Services If your startup already utilizes cloud services like AWS, Google Cloud, or Microsoft Azure, consider leveraging their built-in AI capabilities. These platforms often provide out-of-the-box AI and machine learning tools that integrate easily with their other services. Leveraging these capabilities can significantly simplify the process of getting started with AI and reduce the initial investment required. 7. Train Your Team Adopting AI isn’t just about technology—it's about people. Ensuring your team is comfortable with AI tools is essential for a successful integration. Provide training sessions to familiarize your employees with the new tools and processes. The more confident your team feels, the more likely they are to use AI effectively and find innovative ways to apply it. 8. Monitor and Optimize AI integration is an ongoing process, not a one-time project. Once you integrate AI tools, it's crucial to monitor their performance and impact on your startup. Collect feedback from the team, track key performance metrics, and continuously optimize AI applications to make sure they are providing the intended value. AI works best when it evolves based on new data and insights. 9. Focus on Privacy and Compliance Startups must also ensure that their use of AI complies with relevant regulations and industry standards. AI often requires a lot of data, some of which may be sensitive. Be sure to follow best practices for data security, privacy, and compliance. This is not only vital for maintaining trust with customers but also for avoiding potential legal headaches down the line. 10. Pilot Before Full Implementation To minimize risks, consider piloting AI tools before fully integrating them. This lets you test the technology in a controlled environment, identify any issues, and evaluate the benefits before rolling it out more broadly. A pilot approach helps to mitigate unexpected challenges and ensure the AI is ready to support your startup's needs effectively. Conclusion Integrating AI into your startup's tech stack can be a game-changer, helping to automate mundane tasks, enhance decision-making, and fuel growth. By following these best practices—starting small, ensuring data quality, collaborating across teams, and leveraging existing cloud services—you can set your startup on a path to successful AI integration. Remember, AI is most effective when it’s approached strategically and incrementally, providing long-term benefits that grow along with your business. Ready to take your startup to the next level with AI integration? Start small, choose the right tools, and don't forget to train your team. Embrace the power of AI, and watch as it helps you create new efficiencies, streamline processes, and gain valuable insights. Start building today Try out the smoothest way to build, launch and manage an app Try for Free -> © Fine.dev - All rights reserved. Product Overview AI Workflows Pricing & Plans Changelog Blog Docs Company Press Terms & Conditions Privacy policy | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/CSS/How_to/Layout_cookbook/Card | Card - CSS | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web CSS How to Layout cookbook Card Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 中文 (简体) Card This pattern is a list of "card" components with optional footers. A card contains a title, an image, a description or other content, and an attribution or footer. Cards are generally displayed within a group or collection. In this article Requirements Recipe Choices made Alternative methods Accessibility concerns See also Requirements Create a group of cards, with each card component containing a heading, image, content, and, optionally, a footer. Each card in the group of cards should be the same height. The optional card footer should stick to the bottom of the card. The cards in the group should line up in two dimensions — both vertically and horizontally. Recipe Click "Play" in the code blocks below to edit the example in the MDN Playground: html <div class="cards"> <article class="card"> <header> <h2>A short heading</h2> </header> <img src="https://mdn.github.io/shared-assets/images/examples/balloons.jpg" alt="Hot air balloons" /> <div class="content"> <p> The idea of reaching the North Pole by means of balloons appears to have been entertained many years ago. </p> </div> </article> <article class="card"> <header> <h2>A short heading</h2> </header> <img src="https://mdn.github.io/shared-assets/images/examples/balloons2.jpg" alt="Hot air balloons" /> <div class="content"> <p>Short content.</p> </div> <footer>I have a footer!</footer> </article> <article class="card"> <header> <h2>A longer heading in this card</h2> </header> <img src="https://mdn.github.io/shared-assets/images/examples/balloons.jpg" alt="Hot air balloons" /> <div class="content"> <p> In a curious work, published in Paris in 1863 by Delaville Dedreux, there is a suggestion for reaching the North Pole by an aerostat. </p> </div> <footer>I have a footer!</footer> </article> <article class="card"> <header> <h2>A short heading</h2> </header> <img src="https://mdn.github.io/shared-assets/images/examples/balloons2.jpg" alt="Hot air balloons" /> <div class="content"> <p> The idea of reaching the North Pole by means of balloons appears to have been entertained many years ago. </p> </div> </article> </div> css body { font: 1.2em sans-serif; } img { max-width: 100%; } .cards { max-width: 700px; margin: 1em auto; display: grid; grid-template-columns: repeat(auto-fill, minmax(230px, 1fr)); grid-gap: 20px; } .card { border: 1px solid #999999; border-radius: 3px; display: grid; grid-template-rows: max-content 200px 1fr; } .card img { object-fit: cover; width: 100%; height: 100%; } .card h2 { margin: 0; padding: 0.5rem; } .card .content { padding: 0.5rem; } .card footer { background-color: #333333; color: white; padding: 0.5rem; } Choices made Each card is laid out using CSS grid layout despite the layout being one-dimensional. This enables the use of content sizing for the grid tracks. To set up a single-column grid we can use the following: css .card { display: grid; grid-template-rows: max-content 200px 1fr; } display: grid converts the element into a grid container. The three values of the grid-template-rows property divide the grid into a minimum of three rows, defining the height of the first three children of the card, in order. Each card contains a <header> , <img> , and <div> , in that order, with some also containing a <footer> . The heading row, or track, is set to max-content , which prevents it from stretching. The image track is set to 200 pixels tall. The third track, where the content lives, is set to 1fr . This means it will fill any additional space. Any children beyond the three with explicitly defined sizes create rows in the implicit grid, which fits the content added to it. These are auto-sized by default. If a card contains a footer, it is auto-sized. The footer, when present, sticks to the bottom of the grid. The footer is auto-sized to fit its content; the content <div> then stretches take up any additional space. The following ruleset creates the grid of cards: css .cards { display: grid; grid-template-columns: repeat(auto-fill, minmax(230px, 1fr)); gap: 20px; } The grid-template-columns property defines the widths of the grid columns. In this case, we set the grid to auto-fill, with repeated columns that are minimally 230px but allowed to grow to fill the available space. The gap property sets a gap of 20px between adjacent rows and adjacent columns. Note: The various elements in separate cards do not align with each other, as each card is an independent grid. Lining up the components in each card with the same components in adjacent cards can be done with subgrid . Alternative methods Flexbox can also be used to lay out each card. With flexbox, the dimensions of each card's rows are set with the flex property on each row, rather than on the card container. With flexbox, the dimensions of the flex items are defined on the children rather than the parent. Whether you choose to use grid or flexbox depends on your preference, whether you prefer controlling the tracks from the container or prefer adding rules to the items. We chose grid for the cards as, generally, you want cards to be lined up both vertically and horizontally. Additionally, lining up the components within each card to the components of adjacent cards can be done with subgrid. Flex has no hack-free equivalent to subgrid. Accessibility concerns Depending on the content of your card, there may be things you could or should do to enhance accessibility. See Inclusive components: Card by Heydon Pickering, for a very detailed explanation of these issues. See also grid-template-columns grid-template-rows gap Inclusive components: Card CSS grid layout module Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 7, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar CSS Guides Modules Anchor positioning Animations Backgrounds and borders Basic user interface Borders and box decorations Box alignment Box model Box sizing Cascading and inheritance Color adjustment Colors Compositing and blending Conditional rules Containment Counter styles CSSOM view Custom functions and mixins Custom highlight API Custom properties for cascading variables Display Easing functions Environment variables Filter effects Flexible box layout Font loading Fonts Fragmentation Generated content Grid layout Images Inline layout Lists and counters Logical properties and values Masking Media queries Motion path Multi-column layout Namespaces Nesting Overflow Overscroll behavior Paged media Positioned layout Properties and values API Pseudo-elements Round display Ruby layout Scoping Scroll anchoring Scroll snap Scroll-driven animations Scrollbars styling Selectors Shadow parts Shapes Syntax Table Text Text decoration Transforms Transitions Values and units View transitions Viewport Writing modes Anchor positioning Using anchor positioning Handling overflow Animations Animatable properties Using animations Backgrounds and borders Using multiple backgrounds Resizing background images Scaling SVG backgrounds Box alignment Overview In block layout In flexbox In grid layout In multi-column layout Box model Introduction Margin collapsing Box sizing Aspect ratios Cascade Introduction Inheritance Specificity Property value processing Shorthand properties Cascading variables Using custom properties Colors Applying color Color values Using relative colors Using color wisely Accessibility: Colors and luminance Accessibility: Color contrast Columns Basic concepts Styling columns Using multi-column layouts Spanning and balancing columns Handling overflow Handling content breaks Conditional rules Using feature queries Using container scroll-state queries Containment Container queries Using containment Using container size and style queries CSSOM view Coordinate systems (API) Viewport concepts Custom functions and mixins Using CSS custom functions Display Block and inline layout Flow layout Flow layout and overflow Flow layout and writing modes In flow and out of flow Layout and the containing block Formatting contexts Block formatting context Inline formatting context Using multi-keyword syntax Visual formatting model Environment variables Using environment variables Filter effects Using filter effects Flexbox Basic concepts Flexbox and other layouts Aligning flex items Ordering flex items Controlling flex item ratios Wrapping flex items Typical use cases Fonts OpenType features Variable fonts WOFF Grid Basic concepts Grid and other layouts Using line-based placement Grid template areas Using named grid lines Using auto-placement Aligning items Logical values and writing modes Grid layout and accessibility Common grid layouts Subgrid Masonry layout Experimental Images Using gradients Using object-view-box Styling replaced elements Implementing image sprites Lists and counters Using counters Indenting lists Logical properties Basic concepts For floating and positioning For margins, borders, and padding For sizing Masking Introduction Clipping Multiple masks Mask properties Media queries Using media queries For accessibility Testing Printing Nesting style rules Nesting at-rules Nesting and specificity Using nesting Overflow Creating carousels Positioning Stacking context Example 1 Example 2 Example 3 Stacking floating elements Understanding z-index Using z-index Stacking without z-index Scroll anchoring Overview Scroll-driven animations Scroll-driven animation timelines Scroll snap Basic concepts Using scroll snap events Selectors Selectors and combinators Selector structure Privacy and :visited Using :target Shapes Overview Box-value shapes Image-based shapes Using shape-outside Syntax Introduction Comments At-rules Error handling Text Wrapping and breaking text Handling whitespace Text decoration Text shadows Transforms Using transforms Transitions Using transitions Values and units Value definition syntax Numeric data types Textual data types Using math functions Using typed arithmetic Writing modes Introduction Vertical form controls How to Layout cookbook Media objects Column layouts Center an element Sticky footers Split navigation Breadcrumb navigation List group with badges Pagination Card Grid wrapper Contribute a recipe Cookbook template Tools Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator Reference Properties -moz-* -moz-float-edge Non-standard Deprecated -moz-force-broken-image-icon Non-standard Deprecated -moz-orient Non-standard -moz-user-focus Non-standard Deprecated -moz-user-input Non-standard Deprecated -webkit-* -webkit-border-before Non-standard -webkit-box-reflect Non-standard -webkit-mask-box-image Non-standard -webkit-mask-composite Non-standard -webkit-mask-position-x Non-standard -webkit-mask-position-y Non-standard -webkit-mask-repeat-x Non-standard -webkit-mask-repeat-y Non-standard -webkit-tap-highlight-color Non-standard -webkit-text-fill-color -webkit-text-security Non-standard -webkit-text-stroke -webkit-text-stroke-color -webkit-text-stroke-width -webkit-touch-callout Non-standard Custom properties (--*): CSS variables accent-color align-* align-content align-items align-self alignment-baseline all anchor-name anchor-scope animation-* animation animation-composition animation-delay animation-direction animation-duration animation-fill-mode animation-iteration-count animation-name animation-play-state animation-range animation-range-end animation-range-start animation-timeline animation-timing-function appearance aspect-ratio backdrop-filter backface-visibility background-* background background-attachment background-blend-mode background-clip background-color background-image background-origin background-position background-position-x background-position-y background-repeat background-size baseline-source block-size border-* border border-block border-block-color border-block-end border-block-end-color border-block-end-style border-block-end-width border-block-start border-block-start-color border-block-start-style border-block-start-width border-block-style border-block-width border-bottom border-bottom-color border-bottom-left-radius border-bottom-right-radius border-bottom-style border-bottom-width border-collapse border-color border-end-end-radius border-end-start-radius border-image border-image-outset border-image-repeat border-image-slice border-image-source border-image-width border-inline border-inline-color border-inline-end border-inline-end-color border-inline-end-style border-inline-end-width border-inline-start border-inline-start-color border-inline-start-style border-inline-start-width border-inline-style border-inline-width border-left border-left-color border-left-style border-left-width border-radius border-right border-right-color border-right-style border-right-width border-spacing border-start-end-radius border-start-start-radius border-style border-top border-top-color border-top-left-radius border-top-right-radius border-top-style border-top-width border-width bottom box-* box-align Non-standard Deprecated box-decoration-break box-direction Non-standard Deprecated box-flex Non-standard Deprecated box-flex-group Non-standard Deprecated box-lines Non-standard Deprecated box-ordinal-group Non-standard Deprecated box-orient Non-standard Deprecated box-pack Non-standard Deprecated box-shadow box-sizing break-* break-after break-before break-inside caption-side caret-* caret Experimental caret-animation Experimental caret-color caret-shape Experimental clear clip-* clip Deprecated clip-path clip-rule color-* color color-interpolation color-interpolation-filters color-scheme column-* column-count column-fill column-gap column-rule column-rule-color column-rule-style column-rule-width column-span column-width columns contain-* contain contain-intrinsic-block-size contain-intrinsic-height contain-intrinsic-inline-size contain-intrinsic-size contain-intrinsic-width container-* container container-name container-type content content-visibility corner-* corner-block-end-shape Experimental corner-block-start-shape Experimental corner-bottom-left-shape Experimental corner-bottom-right-shape Experimental corner-bottom-shape Experimental corner-end-end-shape Experimental corner-end-start-shape Experimental corner-inline-end-shape Experimental corner-inline-start-shape Experimental corner-left-shape Experimental corner-right-shape Experimental corner-shape Experimental corner-start-end-shape Experimental corner-start-start-shape Experimental corner-top-left-shape Experimental corner-top-right-shape Experimental corner-top-shape Experimental counter-* counter-increment counter-reset counter-set cursor cx cy d direction display dominant-baseline dynamic-range-limit empty-cells field-sizing fill-* fill fill-opacity fill-rule filter flex-* flex flex-basis flex-direction flex-flow flex-grow flex-shrink flex-wrap float flood-color flood-opacity font-* font font-family font-feature-settings font-kerning font-language-override font-optical-sizing font-palette font-size font-size-adjust font-smooth Non-standard font-stretch Deprecated font-style font-synthesis font-synthesis-position Experimental font-synthesis-small-caps font-synthesis-style font-synthesis-weight font-variant font-variant-alternates font-variant-caps font-variant-east-asian font-variant-emoji font-variant-ligatures font-variant-numeric font-variant-position font-variation-settings font-weight forced-color-adjust gap grid-* grid grid-area grid-auto-columns grid-auto-flow grid-auto-rows grid-column grid-column-end grid-column-start grid-row grid-row-end grid-row-start grid-template grid-template-areas grid-template-columns grid-template-rows hanging-punctuation height hyphenate-character hyphenate-limit-chars hyphens image-* image-orientation image-rendering image-resolution Experimental initial-letter inline-size inset-* inset inset-block inset-block-end inset-block-start inset-inline inset-inline-end inset-inline-start interactivity Experimental interest-* interest-delay Experimental interest-delay-end Experimental interest-delay-start Experimental interpolate-size Experimental isolation justify-* justify-content justify-items justify-self left letter-spacing lighting-color line-* line-break line-clamp line-height line-height-step Experimental list-* list-style list-style-image list-style-position list-style-type margin-* margin margin-block margin-block-end margin-block-start margin-bottom margin-inline margin-inline-end margin-inline-start margin-left margin-right margin-top margin-trim Experimental marker-* marker marker-end marker-mid marker-start mask-* mask mask-border mask-border-mode mask-border-outset mask-border-repeat mask-border-slice mask-border-source mask-border-width mask-clip mask-composite mask-image mask-mode mask-origin mask-position mask-repeat mask-size mask-type math-* math-depth math-shift math-style max-* max-block-size max-height max-inline-size max-width min-* min-block-size min-height min-inline-size min-width mix-blend-mode object-* object-fit object-position object-view-box Experimental offset-* offset offset-anchor offset-distance offset-path offset-position offset-rotate opacity order orphans outline-* outline outline-color outline-offset outline-style outline-width overflow-* overflow overflow-anchor overflow-block overflow-clip-margin overflow-inline overflow-wrap overflow-x overflow-y overlay Experimental overscroll-* overscroll-behavior overscroll-behavior-block overscroll-behavior-inline overscroll-behavior-x overscroll-behavior-y padding-* padding padding-block padding-block-end padding-block-start padding-bottom padding-inline padding-inline-end padding-inline-start padding-left padding-right padding-top page-* page page-break-after Deprecated page-break-before Deprecated page-break-inside Deprecated paint-order perspective perspective-origin place-* place-content place-items place-self pointer-events position-* position position-anchor position-area position-try position-try-fallbacks position-try-order position-visibility print-color-adjust quotes r reading-flow Experimental reading-order Experimental resize right rotate row-gap ruby-* ruby-align ruby-overhang ruby-position rx ry scale scroll-* scroll-behavior scroll-margin scroll-margin-block scroll-margin-block-end scroll-margin-block-start scroll-margin-bottom scroll-margin-inline scroll-margin-inline-end scroll-margin-inline-start scroll-margin-left scroll-margin-right scroll-margin-top scroll-marker-group Experimental scroll-padding scroll-padding-block scroll-padding-block-end scroll-padding-block-start scroll-padding-bottom scroll-padding-inline scroll-padding-inline-end scroll-padding-inline-start scroll-padding-left scroll-padding-right scroll-padding-top scroll-snap-align scroll-snap-stop scroll-snap-type scroll-target-group Experimental scroll-timeline scroll-timeline-axis scroll-timeline-name scrollbar-* scrollbar-color scrollbar-gutter scrollbar-width shape-* shape-image-threshold shape-margin shape-outside shape-rendering speak-as Experimental stop-color stop-opacity stroke-* stroke stroke-dasharray stroke-dashoffset stroke-linecap stroke-linejoin stroke-miterlimit stroke-opacity stroke-width tab-size table-layout text-* text-align text-align-last text-anchor text-autospace text-box text-box-edge text-box-trim text-combine-upright text-decoration text-decoration-color text-decoration-inset Experimental text-decoration-line text-decoration-skip Experimental text-decoration-skip-ink text-decoration-style text-decoration-thickness text-emphasis text-emphasis-color text-emphasis-position text-emphasis-style text-indent text-justify text-orientation text-overflow text-rendering text-shadow text-size-adjust Experimental text-spacing-trim Experimental text-transform text-underline-offset text-underline-position text-wrap text-wrap-mode text-wrap-style timeline-scope top touch-action transform-* transform transform-box transform-origin transform-style transition-* transition transition-behavior transition-delay transition-duration transition-property transition-timing-function translate unicode-bidi user-modify Non-standard Deprecated user-select vector-effect vertical-align view-* view-timeline view-timeline-axis view-timeline-inset view-timeline-name view-transition-class view-transition-name visibility white-space white-space-collapse widows width will-change word-break word-spacing writing-mode x y z-index zoom Selectors & nesting selector Attribute selectors Class selectors ID selectors Keyframe selectors Namespace separator Selector list Type selectors Universal selectors Combinators Child combinator Column combinator Experimental Descendant combinator Next-sibling combinator Subsequent-sibling combinator Pseudo-classes :-moz-* :-moz-broken Non-standard Deprecated :-moz-drag-over Non-standard :-moz-first-node Experimental Non-standard :-moz-handler-blocked Non-standard :-moz-handler-crashed Non-standard :-moz-handler-disabled Non-standard :-moz-last-node Experimental Non-standard :-moz-loading Non-standard :-moz-locale-dir(ltr) Non-standard :-moz-locale-dir(rtl) Non-standard :-moz-only-whitespace Non-standard :-moz-submit-invalid Non-standard :-moz-suppressed Non-standard :-moz-user-disabled Non-standard :-moz-window-inactive Non-standard :active-* :active :active-view-transition :active-view-transition-type() :any-link :autofill :blank Experimental :buffering :checked :current Experimental :default :defined :dir() :disabled :empty :enabled :first-* :first :first-child :first-of-type :focus-* :focus :focus-visible :focus-within :fullscreen :future :has-slotted :has() :heading Experimental :heading() Experimental :host :host-context() Deprecated :host() :hover :in-range :indeterminate :interest-source Experimental :interest-target Experimental :invalid :is() :lang() :last-child :last-of-type :left :link :local-link Experimental :modal :muted :not() :nth-* :nth-child() :nth-last-child() :nth-last-of-type() :nth-of-type() :only-child :only-of-type :open :optional :out-of-range :past :paused :picture-in-picture :placeholder-shown :playing :popover-open :read-only :read-write :required :right :root :scope :seeking :stalled :state() :target-* :target :target-after Experimental :target-before Experimental :target-current Experimental :user-invalid :user-valid :valid :visited :volume-locked :where() Pseudo-elements ::-moz-* ::-moz-color-swatch Non-standard ::-moz-focus-inner Non-standard Deprecated ::-moz-list-bullet Experimental Non-standard ::-moz-list-number Experimental Non-standard ::-moz-meter-bar Non-standard ::-moz-progress-bar Experimental Non-standard ::-moz-range-progress Non-standard ::-moz-range-thumb Non-standard ::-moz-range-track Non-standard ::-webkit-* ::-webkit-inner-spin-button Non-standard ::-webkit-meter-bar Non-standard Deprecated ::-webkit-meter-even-less-good-value Non-standard ::-webkit-meter-inner-element Non-standard ::-webkit-meter-optimum-value Non-standard ::-webkit-meter-suboptimum-value Non-standard ::-webkit-progress-bar Non-standard ::-webkit-progress-inner-element Non-standard ::-webkit-progress-value Non-standard ::-webkit-scrollbar Non-standard ::-webkit-search-cancel-button Non-standard ::-webkit-search-results-button Non-standard ::-webkit-slider-runnable-track Non-standard ::-webkit-slider-thumb Non-standard ::after ::backdrop ::before ::checkmark Experimental ::column Experimental ::cue ::details-content ::file-selector-button ::first-letter ::first-line ::grammar-error ::highlight() ::marker ::part() ::picker-icon Experimental ::picker() Experimental ::placeholder ::scroll-* ::scroll-button() Experimental ::scroll-marker Experimental ::scroll-marker-group Experimental ::selection ::slotted() ::spelling-error ::target-text ::view-* ::view-transition ::view-transition-group() ::view-transition-image-pair() ::view-transition-new() ::view-transition-old() At-rules @charset @color-profile @container @counter-style @custom-media Experimental @document Non-standard Deprecated @font-face @font-feature-values @font-palette-values @function Experimental @import @keyframes @layer @media @namespace @page @position-try @property @scope @starting-style @supports @view-transition Values !important fit-content inherit initial max-content min-content revert revert-layer rule-list unset Types <absolute-size> <alpha-value> <angle-percentage> <angle> <axis> <baseline-position> <basic-shape> <blend-mode> <box-edge> <calc-keyword> <calc-sum> <color-interpolation-method> <color> <content-distribution> <content-position> <corner-shape-value> Experimental <custom-ident> <dashed-function> Experimental <dashed-ident> <dimension> <display-box> <display-inside> <display-internal> <display-legacy> <display-listitem> <display-outside> <easing-function> <filter-function> <flex> <frequency-percentage> <frequency> <generic-family> <gradient> <hex-color> <hue-interpolation-method> <hue> <ident> <image> <integer> <length-percentage> <length> <line-style> <named-color> <number> <overflow-position> <overflow> <percentage> <position-area> <position> <ratio> <relative-size> <resolution> <self-position> <shape> Deprecated <string> <system-color> <text-edge> <time-percentage> <time> <timeline-range-name> <transform-function> <url> Functions -moz-image-rect Non-standard Deprecated abs() acos() anchor-size() anchor() asin() atan() atan2() attr() blur() brightness() calc-size() Experimental calc() circle() clamp() color-mix() color() conic-gradient() contrast-color() contrast() cos() counter() counters() cross-fade() cubic-bezier() device-cmyk() drop-shadow() dynamic-range-limit-mix() Experimental element() Experimental ellipse() env() exp() fit-content() grayscale() hsl() hue-rotate() hwb() hypot() if() Experimental image-set() image() inset() invert() lab() lch() light-dark() linear-gradient() linear() log() matrix() matrix3d() max() min() minmax() mod() oklab() oklch() opacity() paint() path() perspective() polygon() pow() progress() radial-gradient() ray() rect() rem() repeat() repeating-conic-gradient() repeating-linear-gradient() repeating-radial-gradient() rgb() rotate() rotate3d() rotateX() rotateY() rotateZ() round() saturate() scale() scale3d() scaleX() scaleY() scaleZ() sepia() shape() sibling-count() sibling-index() sign() sin() skew() skewX() skewY() sqrt() steps() superellipse() Experimental symbols() tan() translate() translate3d() translateX() translateY() translateZ() type() Experimental url() var() xywh() Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fsuprsend&trk=organization_guest_main-feed-card_share-cta | Sign Up | LinkedIn Join LinkedIn now — it’s free! Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Remember me First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:26 |
https://docs.devcycle.com/sdk/features | Features and Functionality | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS Server-side SDKS SDK Proxy SDK Features On this page Features and Functionality DevCycle strives to ensure that all our APIs and SDKs have identical functionality (except language- or platform-specific nuances). Below is a list of all the current functionality that DevCycle supports across the SDKs. Universal Initialization Evaluating Features & Using Variables Getting All Features Getting All Variables Identifying Users / Setting Properties Tracking Events Realtime Updates Limited Custom Domains Initialization Client-Side SDKs For most client-side SDKs, the only required parameters to initialize the SDK are the SDK Key and the current user. The SDK key is unique to each Project and Environment and can be found in the DevCycle dashboard. The current user is determined by you, and should contain any details about the user that you require for your targeting logic. A typical initialization call looks like this const devcycleClient = initializeDevCycle ( '<DEVCYCLE_CLIENT_SDK_KEY>' , user ) SDKs also offer a way to wait for initialization to finish, meaning that the DevCycle configuration has been obtained and the SDK is ready to return the correct Variable values for the given user. Here is a Javascript example: // wait for client to initialize await devcycleClient . onClientInitialized ( ) Caching of Configurations When initialized, each client-side SDK will cache the retrieved configuration for the user. This cache will be used in scenarios where on subsequent initializations a new configuration is not available. This may be due to a lack of internet connection or a lack of connection to DevCycle. Additionally, if the SDK is interacted with before any initialization (such as attempting to read a Variable far early on in an application before initialization), the cached value will be read. If a Variable is first read from the cache and you've implemented a listener for realtime updates , once a new value is retrieved after initialization, the onUpdate function on the Variable will be triggered and return updated values. Server-Side SDKs For most server-side SDKs, the only required parameter to initialize the SDK is the SDK Key. The SDK key is unique to each Project and Environment and can be found in the DevCycle dashboard. A typical initialization call looks like this const devcycleClient = initializeDevCycle ( '<DEVCYCLE_SERVER_SDK_KEY>' ) SDKs also offer a way to wait for initialization to finish, meaning that the DevCycle configuration has been obtained and the SDK is ready to return the correct Variable values for the given user. Here is a Javascript example: // wait for client to initialize await devcycleClient . onClientInitialized ( ) Evaluating Features & Using Variables This section explains how to use retrieve the Variables of a Feature as well as use their values. For information on setting up a Feature for use, read Variables and Variations and Targeting Users Every SDK provides a method to retrieve a Variable's value. It expects to receive the unique key of the Variable, and a default value to serve in case no other value is available. A typical Variable method would look something like this: const myVariableValue = devcycleClient . variableValue ( // Variable "key" 'my-variable-key' , // Default value to use if DevCycle has no other value 'default-value' , ) Each call to this method is tracked as an "evaluation" event. These events will be shown in the DevCycle dashboard and are used to power the analytics graphs that allow you to see the effects of your Variables being used. The default value will be returned in the following scenarios: The SDK has not yet finished initializing and obtaining a configuration from DevCycle There was an error reaching the DevCycle servers and the configuration could not be obtained The Variable does not exist in DevCycle The default value's type does not align with the type of the Variable being served from DevCycle. For example, a Boolean default value will be used if the DevCycle configuration is trying to set this Variable to a String value. This preserves type safety and prevents the remote configuration from breaking your application at runtime. The SDK has finished initializing, but the user has not been targeted for a Feature that controls this Variable For more information on how the default value is used, see Variable Defaults . Evaluation Reasons When a Variable is evaluated in DevCycle, the response includes metadata explaining why a specific Variation's value was returned. This is captured in the eval object, which helps teams debug and understand Feature Flag decisions more effectively. DevCycle extends the OpenFeature Evaluation Details structure with additional reason types and optional fields for richer context. Supported SDKs SDK / Platform Minimum Version with eval metadata Android 2.5.0 Flutter 1.11.0 iOS 1.24.0 JavaScript (Web) 1.41.0 Next.js 2.17.0 NestJS 0.26.0 React 1.39.0 React Native 2.16.0 React Native (Expo) 2.16.0 Go Server v2.23.0 Java Server 2.8.0 JavaScript Server (Cloud) 1.27.0 Node.js Server (Local) 1.41.0 .NET Server (Cloud) 3.6.0 .NET Server (Local) 4.6.0 PHP Server 2.2.0 Python Server 3.12.0 Ruby Server 3.7.0 Evaluation Object Format "eval" : { "reason" : "REASON_ENUM" , "details" : "optional string" , "target_id" : "optional string" } Field Type Description reason string A required enum value indicating why a specific value was returned. details string An optional string providing extra context about the evaluation outcome. target_id string An optional identifier for the matched targeting rule or audience. Reason Types The reason field reflects the primary reason a particular value was served. Here are the possible values: Reason Description Examples of details Property DEFAULT Returned when the default value was used. This may occur due to a type mismatch, a missing configuration, or an error in evaluation logic. - Type Mismatch - User Not Targeted - (no details if unknown) TARGETING_MATCH Indicates the user matched a targeting rule or audience and was served the corresponding Variation. - Audience Match → Country AND Email AND App Version - Custom Data → full_country - Country AND Custom Data → isBetaUser SPLIT The user matched targeting rules and was bucketed into a Variation using a percentage rollout or random distribution. Implies a TARGETING_MATCH . - Rollout | Custom Data → full_country - Random Distribution | isBetaUser OVERRIDE The result was manually overridden via API/CLI override or self-targeting, typically in local development or QA. - Override OPT_IN The user explicitly opted into (or out of) a specific Variation using DevCycle’s Opt-In feature. - Opt-In ERROR An error occurred during evaluation, resulting in the default value being served. - Missing Environment config - SDK not initialized Additional Notes The details and target_id fields are included only when relevant. Not all reasons will include these fields—if no helpful context is available, they will be omitted. Getting All Features The "Get All Features" function in an SDK will return a map of all the Features that the user is currently receiving. The response is the following general format, with slight changes depending on the specifics of the SDK: { "your-cool-feature" : { "key" : "your-cool-feature" , "type" : "release" , "variationKey" : "variation-on" , "variationName" : "Variation On" , "_id" : "123456" , "_variation" : "333345" } , "another-feature" : { "key" : "another-feature" , "type" : "ops" , "variationKey" : "enabled" , "variationName" : "Enabled" , "_id" : "123456" , "_variation" : "444123" } } Only Features that the User has satisfied Targeting Rules for will be returned by this function. The Feature must also be enabled for that Environment. Getting all Variables The "Get All Variables" function in an SDK will return a map of all the Variables that the user is receiving. The response is the following general format, with slight changes depending on the specifics of the SDK: { "my-feature-variable" : { "_id" : "617c19199db63239d2d17025" , "key" : "my-feature-variable" , "type" : "Boolean" , "value" : false } , "some-string-variable" : { "_id" : "61828f25c1c23bc6ae1366e9" , "key" : "some-string-variable" , "type" : "String" , "value" : "this is a string variable value" } } Only Variables in Features that the user has satisfied Targeting Rules for will be part of the response in this method. The Feature must also be enabled for the Environment this SDK is being called on. caution This method is intended to be used for debugging and analytics purposes, not as a method for retrieving the value of Variables to change code behaviour. For that purpose, we strongly recommend using the individual Variable access method described in Evaluating Features & Using Variables . Using the "Get All Variables" method instead will result in no evaluation events being tracked for individual Variables, which will not allow the use of other DevCycle Features such as Code Usage detection . Identifying a User or Setting Properties All SDKs have the concept of a user "identity" to be used for evaluating Feature Targeting Rules. The Features that are served to a user will be a function of the Targeting Rules and the user data you provide to the SDK. tip While we refer to these identities as "users", the data passed here can represent anything you want to target against. In these cases, you can use any string that makes sense as an identifier as the "user_id". The id simply needs to be consistent to ensure consistent random distributions and rollouts. The user data object that you should use across SDKs should look something like this: { "user_id" : " [email protected] " , "name" : "user 1 name" , "customData" : { "customKey" : "customValue" } , "privateCustomData" : { "privateKey" : "privateValue" } } The identification of users functions differently on Client SDKs vs. Server SDKs. Client SDK Identification Client SDKs can be initialized with a user object if the user data is known at that time. All client SDKs accept a "user" argument in their initialization function. By providing the user here, the SDK's initial configuration request will be made with that data and the correct Variable values will be available once the SDK initializes. For that reason, providing user data during initialization is recommended where possible. Identifying a user can also be accomplished later by calling the identifyUser function and providing your user data object. When this method is called, the SDK will retrieve a new configuration from the DevCycle servers corresponding to that user. A typical call to this method looks like const user = { user_id : 'myUser' , } await devCycleClient . identifyUser ( user ) The identifyUser method always includes a way to wait for the operation to finish. When finished, the SDK will have the correct configuration for the given user and all Variable evaluations from that point onward will be based on the new user's data. This method is useful when user data can not be known at initialization time, or when the user's identity must be changed during the application's lifecycle. Anonymous Users info If a user id is not supplied, client-side SDKs will automatically generate an anonymous user id and assign it to the current user. Anonymous users count towards your MAUs for the month. This id will be cached and used between app sessions / website visits until a user id is supplied or reset is called. This ensures that you will not experience a rise in MAUs if the main experience of your application is in a logged-out or anonymous state. Resetting a User Client SDKs also contain a method for "resetting" a user's identity. This can be used in cases like "logging out", where there is no longer any identifiable information to pass to the SDK. In those cases, "reset" will clear all stored data and generate a new "anonymous" user ID to represent the user. Custom Data and Private Custom Data User data can also contain "custom data", which is a key-value map of any arbitrary data you want to use for targeting. The provided data can be used in Targeting Rules by creating Custom Properties in the DevCycle dashboard. Learn more about Custom Property Targeting . When setting custom properties you have a choice between keeping that data completely private or allowing for the data to be logged back to DevCycle's events database. Both options allow for the same targeting capabilities, but you should use Private Custom Data if you are looking to avoid having user data saved to any external system. With Private Custom Data, data is used solely for targeting decisions within DevCycle's Edge Workers. It is then discarded and no record is saved anywhere. With regular Custom Data, the data used for evaluation purposes is logged back to DevCycle's events database where it can be used for debugging purposes or providing guidance on evaluation reasons. Server-Side SDK Identification Unlike the Client-Side SDKs, Server-Side SDKs work in a multi-user context. Because of this, a single Identify function does not make sense. Instead, you must provide the user data to each function call when evaluating Variables. For example: const user = { user_id : 'myUser' , } const myVariableValue = devcycleClient . variableValue ( // User data user , // Variable "key" 'my-variable-key' , // Default value to use if DevCycle has no other value 'default-value' , ) In Local Bucketing mode (the default), these calls will quickly compute the Variable value locally using the currently stored DevCycle configuration, and no network calls will be made. Tracking Custom Events The Track function in the DevCycle SDKs allows you to send custom events which can be used for your own data analysis on enabled Features, and Metrics on A/B tests and experiments within the DevCycle dashboard. Here is an example of a custom event request and properties that an event may contain. event = { type : 'button_clicked' , // required field date : new Date ( ) , target : 'my_target' , value : 5 , metaData : { key : 'value' , } , } devcycleClient . track ( event ) Custom Domains When using client-side SDKs, particularly web client SDKs there is the potential for Ad Blockers and browser privacy features to block requests and third-party cookies. Custom Domains with DevCycle ensures all cookies and requests used are first-party and will not be blocked by ensuring requests are sent through your recognized domain. A DNS CNAME needs to be created to leverage this feature. Setting Up Custom Domains Custom Domains are available to those on a business or enterprise plan and require manual setup on both your end as well as DevCycle's. If you are interested in getting set up, please read more on our Custom Domains page, and reach out to [email protected] with the required details. Realtime Updates All DevCycle SDKs are capable of being notified in realtime that new configuration changes have been made in the DevCycle platform. DevCycle leverages Server-Sent Events (SSE) to notify the SDKs that a Feature (Targeting Rules, Variable values, etc.) has been updated and that they should fetch the new configuration. A connection URL is included in the config that the SDK fetches, triggering the SDK to open a connection with our SSE provider and listen for any changes in the given Environment. SDK Specifics Javascript SDK , React SDK If the user loses focus on the webpage for longer then the inactivityDelay (the default of which is set to 2 minutes, and can be configured through the options), the SDK will disconnect from the SSE provider and will reconnect when the user opens the tab / window again (i.e. the page's visibility state = visible ). The SDK will also request a new configuration during reconnection to receive any updates it may have missed while the realtime connection was closed. iOS SDK , Android SDK & Flutter SDK If the user backgrounds the application for some period of time, the SDK will disconnect from the SSE provider and will reconnect again when the user brings the application to the foreground. When the application is brought to the foreground the SDK will request a new configuration to receive any updates it may have missed while the realtime connection was closed. Server-Side SDKs If the server loses its connection it will be re-opened automatically after a configurable interval. Local and Cloud Bucketing Server SDKs have two modes, "Local Bucketing" and "Cloud Bucketing". Local Bucketing Local Bucketing does all targeting decisions locally inside the server running the SDK. The DevCycle configuration is downloaded upon initialization of the SDK, and all future SDK calls will determine flag values based on this data and the provided user data. This approach will guarantee instantaneous, synchronous results from the SDK. Cloud Bucketing The SDK determines flag values by making an API call for each decision, using workers at the edge which are available globally. Every function within the SDK will reach out to these edge workers and respond with extremely low latency. Cloud bucketing is required to use specific features such as EdgeDB and Feature Opt-In . If you aren't using these features, then Local Bucketing is the recommended mode. Server SDK Diagrams The following diagrams illustrate the initialization flow, and logical background processes created/managed by the SDKs. For more information on the architecture of DevCycle services and SDKs, visit the System Architecture page. Initialization Flow Config Manager Event Manager Edit this page Last updated on Jan 9, 2026 Previous SDK Lifecycle Next JavaScript SDK Initialization Client-Side SDKs Server-Side SDKs Evaluating Features & Using Variables Evaluation Reasons Supported SDKs Evaluation Object Format Reason Types Getting All Features Getting all Variables Identifying a User or Setting Properties Client SDK Identification Server-Side SDK Identification Tracking Custom Events Custom Domains Realtime Updates SDK Specifics Local and Cloud Bucketing Local Bucketing Cloud Bucketing Server SDK Diagrams Initialization Flow Config Manager Event Manager DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes | Global attributes - HTML | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTML Reference Global attributes Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) Global attributes Global attributes are attributes common to all HTML elements; they can be used on all elements, though they may have no effect on some elements. Global attributes may be specified on all HTML elements , even those not specified in the standard . That means that any non-standard elements must still permit these attributes, even though using those elements means that the document is no longer HTML5-compliant. For example, HTML5-compliant browsers hide content marked as <foo hidden>…</foo> , even though <foo> is not a valid HTML element. In addition to the basic HTML global attributes, the following global attributes also exist: xml:lang and xml:base — these are inherited from the XHTML specifications and deprecated, but kept for compatibility purposes. The ARIA role attribute and the multiple aria-* states and properties, used for ensuring accessibility. The event handler attributes listed below. In this article List of global attributes List of global event handler attributes Specifications Browser compatibility See also List of global attributes accesskey Provides a hint for generating a keyboard shortcut for the current element. This attribute consists of a space-separated list of characters. The browser should use the first one that exists on the computer keyboard layout. anchor Non-standard Associates a positioned element with an anchor element. The attribute's value is the id value of the element you want to anchor the positioned element to. The element can then be positioned using CSS anchor positioning . autocapitalize Controls whether inputted text is automatically capitalized and, if so, in what manner. autocorrect Controls whether input text is automatically corrected for spelling errors. This can be applied to elements that have editable text except for <input> elements with the attribute: type="password" , type="email" , or type="url" . autofocus Indicates that an element is to be focused on page load, or as soon as the <dialog> it is part of is displayed. This attribute is a boolean, initially false. class A space-separated list of the classes of the element. Classes allow CSS and JavaScript to select and access specific elements via the class selectors or functions like the method Document.getElementsByClassName() . contenteditable An enumerated attribute indicating if the element should be editable by the user. If so, the browser modifies its widget to allow editing. The attribute must take one of the following values: true or the empty string , which indicates that the element must be editable; false , which indicates that the element must not be editable. plaintext-only , which indicates the element's raw text is editable, but rich text formatting is disabled. data-* Forms a class of attributes, called custom data attributes, that allow proprietary information to be exchanged between the HTML and its DOM representation that may be used by scripts. All such custom data are available via the HTMLElement interface of the element the attribute is set on. The HTMLElement.dataset property gives access to them. dir An enumerated attribute indicating the directionality of the element's text. It can have the following values: ltr , which means left to right and is to be used for languages that are written from the left to the right (like English); rtl , which means right to left and is to be used for languages that are written from the right to the left (like Arabic); auto , which lets the user agent decide. It uses a basic algorithm as it parses the characters inside the element until it finds a character with a strong directionality, then it applies that directionality to the whole element. draggable An enumerated attribute indicating whether the element can be dragged, using the Drag and Drop API . It can have the following values: true , which indicates that the element may be dragged false , which indicates that the element may not be dragged. enterkeyhint Hints what action label (or icon) to present for the enter key on virtual keyboards. exportparts Used to transitively export shadow parts from a nested shadow tree into a containing light tree. hidden An enumerated attribute indicating that the element is not yet, or is no longer, relevant . For example, it can be used to hide elements of the page that can't be used until the login process has been completed. The browser won't render such elements. This attribute must not be used to hide content that could legitimately be shown. id Defines a unique identifier (ID) which must be unique in the whole document. Its purpose is to identify the element when linking (using a fragment identifier), scripting, or styling (with CSS). inert A boolean value that makes the browser disregard user input events for the element. Useful when click events are present. inputmode Provides a hint to browsers about the type of virtual keyboard configuration to use when editing this element or its contents. Used primarily on <input> elements, but is usable on any element while in contenteditable mode. is Allows you to specify that a standard HTML element should behave like a registered customized built-in element (see Using custom elements for more details). Note: The item* attributes are part of the WHATWG HTML Microdata feature . itemid The unique, global identifier of an item. itemprop Used to add properties to an item. Every HTML element may have an itemprop attribute specified, where an itemprop consists of a name and value pair. itemref Properties that are not descendants of an element with the itemscope attribute can be associated with the item using an itemref . It provides a list of element ids (not itemid s) with additional properties elsewhere in the document. itemscope itemscope (usually) works along with itemtype to specify that the HTML contained in a block is about a particular item. itemscope creates the Item and defines the scope of the itemtype associated with it. itemtype is a valid URL of a vocabulary (such as schema.org ) that describes the item and its properties context. itemtype Specifies the URL of the vocabulary that will be used to define itemprop s (item properties) in the data structure. itemscope is used to set the scope of where in the data structure the vocabulary set by itemtype will be active. lang Helps define the language of an element: the language that non-editable elements are in, or the language that editable elements should be written in by the user. The attribute should contain a valid BCP 47 language tag . xml:lang has priority over it. nonce A cryptographic nonce ("number used once") which can be used by Content Security Policy to determine whether or not a given fetch will be allowed to proceed. part A space-separated list of the part names of the element. Part names allows CSS to select and style specific elements in a shadow tree via the ::part pseudo-element. popover Used to designate an element as a popover element (see Popover API ). Popover elements are hidden via display: none until opened via an invoking/control element (i.e., a <button> or <input type="button"> with a popovertarget attribute) or a HTMLElement.showPopover() call. role Roles define the semantic meaning of content, allowing screen readers and other tools to present and support interaction with an object in a way that is consistent with user expectations of that type of object. roles are added to HTML elements using role="role_type" , where role_type is the name of a role in the ARIA specification. slot Assigns a slot in a shadow DOM shadow tree to an element: An element with a slot attribute is assigned to the slot created by the <slot> element whose name attribute's value matches that slot attribute's value. spellcheck An enumerated attribute defines whether the element may be checked for spelling errors. It may have the following values: empty string or true , which indicates that the element should be, if possible, checked for spelling errors; false , which indicates that the element should not be checked for spelling errors. style Contains CSS styling declarations to be applied to the element. Note that it is recommended for styles to be defined in a separate file or files. This attribute and the <style> element have mainly the purpose of allowing for quick styling, for example for testing purposes. tabindex An integer attribute indicating if the element can take input focus (is focusable ), if it should participate to sequential keyboard navigation, and if so, at what position. It can take several values: a negative value means that the element should be focusable, but should not be reachable via sequential keyboard navigation; 0 means that the element should be focusable and reachable via sequential keyboard navigation, but its relative order is defined by the platform convention; a positive value means that the element should be focusable and reachable via sequential keyboard navigation; the order in which the elements are focused is the increasing value of the tabindex . If several elements share the same tabindex, their relative order follows their relative positions in the document. title Contains a text representing advisory information related to the element it belongs to. Such information can typically, but not necessarily, be presented to the user as a tooltip. translate An enumerated attribute that is used to specify whether an element's attribute values and the values of its Text node children are to be translated when the page is localized, or whether to leave them unchanged. It can have the following values: empty string or yes , which indicates that the element will be translated. no , which indicates that the element will not be translated. virtualkeyboardpolicy Experimental An enumerated attribute used to control the on-screen virtual keyboard behavior on devices such as tablets, mobile phones, or other devices where a hardware keyboard may not be available for elements that its content is editable (for example, it is an <input> or <textarea> element, or an element with the contenteditable attribute set). auto or an empty string , which automatically shows the virtual keyboard when the element is focused or tapped. manual , which decouples focus and tap on the element from the virtual keyboard's state. writingsuggestions An enumerated attribute indicating if browser-provided writing suggestions should be enabled under the scope of the element or not. false , which disables the browser's writing suggestions. true or an empty string , which enables writing suggestions. List of global event handler attributes HTML event handler attributes are discouraged; see HTML attribute reference for how they work. While the attributes listed below apply to all elements, they are not useful on all elements. For example, onvolumechange HTML attribute is accepted by all elements and attaches an event listener for volumechange , but only media elements will ever receive a volumechange event fired by the browser. For other elements, you can only use EventTarget.dispatchEvent() to manually dispatch one. Some attributes can be specified on <body> , but they would instead listen to events on window . onabort onanimationcancel onanimationend onanimationiteration onanimationstart onauxclick onbeforeinput onbeforematch onbeforetoggle onblur oncancel oncanplay oncanplaythrough onchange onclick onclose oncommand oncontentvisibilityautostatechange oncontextlost oncontextmenu oncontextrestored oncopy oncuechange oncut ondblclick ondrag ondragend ondragenter ondragleave ondragover ondragstart ondrop ondurationchange onemptied onended onerror onfocus onfocusin onfocusout onformdata onfullscreenchange onfullscreenerror ongesturechange Non-standard ongestureend Non-standard ongesturestart Non-standard ongotpointercapture oninput oninvalid onkeydown onkeypress Deprecated onkeyup onload onloadeddata onloadedmetadata onloadstart onlostpointercapture onmousedown onmouseenter onmouseleave onmousemove onmouseout onmouseover onmouseup onmousewheel Deprecated Non-standard onpaste onpause onplay onplaying onpointercancel onpointerdown onpointerenter onpointerleave onpointermove onpointerout onpointerover onpointerrawupdate onpointerup onprogress onratechange onreset onresize onscroll onscrollend onscrollsnapchange Experimental onscrollsnapchanging Experimental onsecuritypolicyviolation onseeked onseeking onselect onselectionchange onselectstart onslotchange onstalled onsubmit onsuspend ontimeupdate ontoggle ontouchcancel ontouchend ontouchmove ontouchstart ontransitioncancel ontransitionend ontransitionrun ontransitionstart onvolumechange onwaiting onwebkitmouseforcechanged Non-standard onwebkitmouseforcedown Non-standard onwebkitmouseforceup Non-standard onwebkitmouseforcewillbegin Non-standard onwheel Specifications Specification HTML # attr-inputmode HTML # the-style-attribute HTML # the-accesskey-attribute HTML # the-popover-attribute HTML # the-id-attribute HTML # inert-subtrees HTML # the-hidden-attribute HTML # attr-spellcheck HTML # attr-enterkeyhint HTML # attr-is HTML # attr-translate HTML # nonce-does-not-update-dom HTML # attr-slot HTML # attr-lang HTML # dom-fe-autofocus HTML # writing-suggestions HTML # attr-autocapitalize HTML # the-dir-attribute HTML # the-title-attribute HTML # classes HTML # the-inert-attribute HTML # the-draggable-attribute HTML # attr-contenteditable HTML # attr-data-* HTML # attr-popover-hint HTML # attr-tabindex HTML # attr-autocorrect HTML # attr-nonce CSS Style Attributes # style-attribute CSS Shadow Parts Module Level 1 # part-attr CSS Shadow Parts Module Level 1 # element-attrdef-html-global-exportparts VirtualKeyboard API # dom-elementcontenteditable-virtualkeyboardpolicy DOM # ref-for-dom-element-slot① Browser compatibility Enable JavaScript to view this browser compatibility table. See also Element interface that allows querying most global attributes. Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 15, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTML Guides Cheatsheet Comments Constraint validation Content categories Date and time formats Microdata Microformats Quirks and standards modes Responsive images How to Define terms with HTML Use data attributes Use cross-origin images Add a hitmap on top of an image Author fast-loading HTML pages Add JavaScript Reference Elements <a> <abbr> <acronym> Deprecated <address> <area> <article> <aside> <audio> <b> <base> <bdi> <bdo> <big> Deprecated <blockquote> <body> <br> <button> <canvas> <caption> <center> Deprecated <cite> <code> <col> <colgroup> <data> <datalist> <dd> <del> <details> <dfn> <dialog> <dir> Deprecated <div> <dl> <dt> <em> <embed> <fencedframe> Experimental <fieldset> <figcaption> <figure> <font> Deprecated <footer> <form> <frame> Deprecated <frameset> Deprecated <h1> <head> <header> <hgroup> <hr> <html> <i> <iframe> <img> <input> <ins> <kbd> <label> <legend> <li> <link> <main> <map> <mark> <marquee> Deprecated <menu> <meta> <meter> <nav> <nobr> Deprecated <noembed> Deprecated <noframes> Deprecated <noscript> <object> <ol> <optgroup> <option> <output> <p> <param> Deprecated <picture> <plaintext> Deprecated <pre> <progress> <q> <rb> Deprecated <rp> <rt> <rtc> Deprecated <ruby> <s> <samp> <script> <search> <section> <select> <selectedcontent> Experimental <slot> <small> <source> <span> <strike> Deprecated <strong> <style> <sub> <summary> <sup> <table> <tbody> <td> <template> <textarea> <tfoot> <th> <thead> <time> <title> <tr> <track> <tt> Deprecated <u> <ul> <var> <video> <wbr> <xmp> Deprecated Attributes accept autocomplete capture content crossorigin dirname disabled elementtiming fetchpriority for form max maxlength min minlength multiple pattern placeholder readonly rel required size step Global attributes accesskey anchor Experimental Non-standard autocapitalize autocorrect autofocus class contenteditable data-* dir draggable enterkeyhint exportparts hidden id inert inputmode is itemid itemprop itemref itemscope itemtype lang nonce part popover slot spellcheck style tabindex title translate virtualkeyboardpolicy Experimental writingsuggestions Attributes by element <input> type <input type="button"> <input type="checkbox"> <input type="color"> <input type="date"> <input type="datetime-local"> <input type="email"> <input type="file"> <input type="hidden"> <input type="image"> <input type="month"> <input type="number"> <input type="password"> <input type="radio"> <input type="range"> <input type="reset"> <input type="search"> <input type="submit"> <input type="tel"> <input type="text"> <input type="time"> <input type="url"> <input type="week"> <script> type importmap speculationrules Experimental <meta> name color-scheme referrer robots theme-color viewport <meta> http-equiv Attribute values rel keywords rel="alternate stylesheet" rel="compression-dictionary" Experimental rel="dns-prefetch" rel="manifest" rel="me" rel="modulepreload" rel="noopener" rel="noreferrer" rel="preconnect" rel="prefetch" rel="preload" rel="prerender" Non-standard Deprecated Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://dev.to/owarup/comment/fndl#main-content | i like this :v - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Discussion on: Episode 1: APIs and Bikes Go Together Great View post Collapse Expand owarup owarup owarup Follow Location mex Work owar at java Joined Sep 26, 2019 • Sep 26 '19 Dropdown menu Copy link Hide i like this :v Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:26 |
https://docs.devcycle.com/platform/security-and-guardrails/permissions/#can--1 | Roles & Permissions | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Approval Workflows Audit Log Custom Property Schemas Feature Obfuscation Roles & Permissions SDK Visibility Variable Schemas Testing and QA Extras Examples Platform Security and Guardrails Roles & Permissions On this page Roles & Permissions At DevCycle, our permissions model is designed to protect production while supporting secure and scalable team collaboration. We offer flexible, role-based access controls that can be applied both at the Organization and Project level—allowing you to tailor access based on how your teams operate. Permissions are available for Organizations on our Business or Enterprise plans. You can visit our pricing page or contact our support team to learn more about our plans. Permission Levels Overview DevCycle supports multiple levels of permission enforcement: Flat Access (default) : All users have full access across all Projects Basic Permissions : Org-wide roles that protect production Environments (Business and Enterprise plans) Full Role-Based Access Control (RBAC) : Fine-grained permissions managed at the Project level (Enterprise plans only) info Permissions enforcement will apply to all Projects and Production-type Environments within your Organization. Basic Permissions (Organization-Wide Roles) Basic permissions apply at the Organization level and are available to all Business and Enterprise customers. The principle behind basic permissions is to protect Production Environments while keeping permissions and their management as lightweight as possible. This level is perfect for teams that want to be able to move fast but still require some governance protections to be in place. info To enable basic permissions, navigate to your Organization Settings page and enable it under the permissions dropdown. The roles available with Basic Permissions are: Members Can ✅ Configure Development and Staging Environments Configure Inactive Production Environments Cannot ❌ Enable or Disable Production Environments Targeting Configure Active Production Environments When Production is Active , Configure Variables and Variations Manage roles of other users Manage Organization or Project settings Publishers Everything Members can do, plus: Can ✅ Enable or Disable Production Environments Targeting Configure Active Production Environments When Production is Active , Configure Variables and Variations Manage Project settings Cannot ❌ Manage roles of other users Manage Organization settings or billing Owners Everything Publishers can do, plus: Can ✅ Manage roles of all users in the Organization Administer billing Assigning Roles To assign a role to a team member, simply navigate to their profile. If you are an owner, you will be able to assign a new role to the member by using the Role dropdown. After you have selected a role, click "save" and the team member's permissions will be updated. For the user to have the new permission level available to them they will need to generate a new session by logging in again. Full Role-Based Access Control (Project-Level Roles – Enterprise Only) For Organizations managing multiple teams or business units, DevCycle offers Project-level RBAC on Enterprise plans. This allows you to manage roles granularly, granting access only to the specific workspaces your team members need with the requisite roles they need in each of those workspaces. With Role-Based Access Control, you can: Scope access to individual Projects Prevent cross-project visibility and restrict access to only the Projects a user is assigned Align access with your SSO groups and SCIM-based provisioning This enables centralized identity and access management with decentralized control, especially when integrated with providers like Azure AD or Okta. info To enable and configure SSO and SCIM-based provisioning, please contact our support team. Role Matrix The table below outlines actions available to each role across Organization and Project levels. note All actions affecting Production Environments are restricted for roles below Publisher . Action Viewer Member Publisher Project Admin Org Admin Org Owner organization:read:settings ✅ ✅ ✅ ✅ ✅ ✅ organization:write:settings ✅ ✅ organization:read:members ✅ ✅ ✅ ✅ ✅ ✅ organization:write:members ✅ ✅ organization:read:billing ✅ ✅ ✅ ✅ ✅ ✅ organization:write:billing ✅ organization:read:projects ✅ ✅ ✅ project:read ✅ ✅ ✅ ✅ ✅ project:write ✅ project:write:settings ✅ ✅ project:delete ✅ feature:read:staleness ✅ ✅ ✅ feature:read ✅ ✅ ✅ ✅ ✅ feature:write ✅ ✅ ✅ ✅ feature:publish ✅ ✅ ✅ feature:delete ✅ ✅ feature:status:archive ✅ ✅ ✅ ✅ feature:status:complete ✅ ✅ ✅ feature:read:config ✅ ✅ ✅ ✅ ✅ feature:write:config ✅ ✅ ✅ ✅ audience:write ✅ ✅ ✅ ✅ audience:read ✅ ✅ ✅ ✅ ✅ audience:write:prod ✅ ✅ ✅ audience:delete ✅ ✅ variable:read ✅ ✅ ✅ ✅ ✅ variable:write ✅ ✅ ✅ ✅ variable:write:prod ✅ ✅ environment:read ✅ ✅ ✅ ✅ ✅ environment:write ✅ ✅ ✅ ✅ environment:delete ✅ ✅ variation:read ✅ ✅ ✅ ✅ ✅ variation:write ✅ ✅ ✅ ✅ variation:delete ✅ ✅ ✅ ✅ results:read ✅ ✅ ✅ ✅ ✅ user:read ✅ ✅ ✅ ✅ ✅ user:write ✅ ✅ ✅ ✅ ✅ auditlog:read ✅ ✅ ✅ ✅ ✅ customproperty:read ✅ ✅ ✅ ✅ ✅ customproperty:write ✅ ✅ ✅ ✅ customproperty:delete ✅ ✅ ✅ ✅ metric:read ✅ ✅ ✅ ✅ ✅ metric:write ✅ ✅ ✅ ✅ metric:delete ✅ ✅ ✅ ✅ metricassociation:read ✅ ✅ ✅ ✅ ✅ metricassociation:write ✅ ✅ ✅ ✅ metricassociation:delete ✅ ✅ ✅ ✅ project:read:overrides ✅ ✅ ✅ ✅ ✅ project:write:overrides ✅ ✅ ✅ ✅ ✅ webhook:read ✅ ✅ ✅ ✅ ✅ webhook:write ✅ ✅ ✅ ✅ webhook:delete ✅ ✅ ✅ project:read:tokens ✅ ✅ project:write:tokens ✅ Managing Role Mappings with SCIM and SSO For Enterprise customers using identity providers (IdPs) like Azure AD or Okta, DevCycle supports role mapping through SCIM and SSO group-based permissions . Roles can be mapped to IdP groups Users are automatically assigned the correct roles upon login Centralized IT control, local team autonomy This streamlines onboarding and offboarding, and ensures the principle of least privilege is maintained. To get started with Role-Based Access Control, contact our support team. Edit this page Last updated on Jan 9, 2026 Previous Feature Obfuscation Next SDK Visibility Permission Levels Overview Basic Permissions (Organization-Wide Roles) Members Publishers Owners Assigning Roles Full Role-Based Access Control (Project-Level Roles – Enterprise Only) Role Matrix Managing Role Mappings with SCIM and SSO DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:26 |
https://www.youtube.com/watch?v=4ObSAa2jREM | Becoming a Great Un-manager - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0xe51fafa5787afa32"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtocjkyVlVhRmloTSjUjZjLBjIKCgJLUhIEGgAgWGLfAgrcAjE1LllUPWFFN21mVl8zZVhrbHd6S1plOTQ1Y2R0S0R0Q1lmQlF6blVNb21nZWRsdHl6RTlWaWM4ZXhvUHJLS0djaFBzcVIxUm9xeWY3MlJpYWROY1dmNmZzYzVQSGJVLXNCYUNiczNSUlRGVEctZklrZUdTYWVBb1h0TFVDNWVTRTJ5eF9BQm51QU5FeTFiVTVFMGlibDRMZVkzZmxoQi1ScC1CaEZ5TzhsbXB6TWpCWWFsbGN6eFB2UXo4S1g0Wk4zMGw2Tm1XdnExVHJIT2hhUTAwM3BwWTNVOFdqVmRZX2FORnNmQVRRS1FfMlJSb2M3NDVqdTJxa3hocC03THJkTWNXYzhSNUY1YS1xWW1YUjJJcEpLZUlSZ2dHOE1VUDBQc3RqVmdiU0twWHREY1VQdGMxakE0NlJfSjU0Vy1lN2JmSjNKYkFjZDlYZTV5RDBpSnE1R2lmQldFUQ%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRb3ZfMnKMMKdfHpxVUkzHf5MpnviNUw83vgHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","badgeViewModel","sheetViewModel","listViewModel","listItemViewModel","avatarStackViewModel","dialogViewModel","dialogHeaderViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","chapterRenderer","notificationActionRenderer","markerRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","macroMarkersListRenderer","macroMarkersListItemRenderer","toggleButtonRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionCourseSectionRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","topicLinkRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtocjkyVlVhRmloTSjUjZjLBjIKCgJLUhIEGgAgWGLfAgrcAjE1LllUPWFFN21mVl8zZVhrbHd6S1plOTQ1Y2R0S0R0Q1lmQlF6blVNb21nZWRsdHl6RTlWaWM4ZXhvUHJLS0djaFBzcVIxUm9xeWY3MlJpYWROY1dmNmZzYzVQSGJVLXNCYUNiczNSUlRGVEctZklrZUdTYWVBb1h0TFVDNWVTRTJ5eF9BQm51QU5FeTFiVTVFMGlibDRMZVkzZmxoQi1ScC1CaEZ5TzhsbXB6TWpCWWFsbGN6eFB2UXo4S1g0Wk4zMGw2Tm1XdnExVHJIT2hhUTAwM3BwWTNVOFdqVmRZX2FORnNmQVRRS1FfMlJSb2M3NDVqdTJxa3hocC03THJkTWNXYzhSNUY1YS1xWW1YUjJJcEpLZUlSZ2dHOE1VUDBQc3RqVmdiU0twWHREY1VQdGMxakE0NlJfSjU0Vy1lN2JmSjNKYkFjZDlYZTV5RDBpSnE1R2lmQldFUQ%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwj20fztkIiSAxXWQTgFHbwdFWYyDHJlbGF0ZWQtYXV0b0jDiI3tmsC08-ABmgEFCAMQ-B3KAQRUkHnc","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=IHZwWFHWa-w\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"IHZwWFHWa-w","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwj20fztkIiSAxXWQTgFHbwdFWYyDHJlbGF0ZWQtYXV0b0jDiI3tmsC08-ABmgEFCAMQ-B3KAQRUkHnc","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=IHZwWFHWa-w\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"IHZwWFHWa-w","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwj20fztkIiSAxXWQTgFHbwdFWYyDHJlbGF0ZWQtYXV0b0jDiI3tmsC08-ABmgEFCAMQ-B3KAQRUkHnc","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=IHZwWFHWa-w\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"IHZwWFHWa-w","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"Becoming a Great Un-manager"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 57회"},"shortViewCount":{"simpleText":"조회수 57회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CMkCELW0CRgAIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESCzRPYlNBYTJqUkVNGmBFZ3MwVDJKVFFXRXlhbEpGVFVBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTHpSUFlsTkJZVEpxVWtWTkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CMkCELW0CRgAIhMI9tH87ZCIkgMV1kE4BR28HRVm"}}],"trackingParams":"CMkCELW0CRgAIhMI9tH87ZCIkgMV1kE4BR28HRVm","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"0","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNQCEKVBIhMI9tH87ZCIkgMV1kE4BR28HRVm"}},{"innertubeCommand":{"clickTrackingParams":"CNQCEKVBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNUCEPqGBCITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNUCEPqGBCITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"4ObSAa2jREM"},"likeParams":"Cg0KCzRPYlNBYTJqUkVNIAAyDAjVjZjLBhCKw_j7AQ%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CNUCEPqGBCITCPbR_O2QiJIDFdZBOAUdvB0VZg=="}}}}}}}]}},"accessibilityText":"이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNQCEKVBIhMI9tH87ZCIkgMV1kE4BR28HRVm","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"1","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNMCEKVBIhMI9tH87ZCIkgMV1kE4BR28HRVm"}},{"innertubeCommand":{"clickTrackingParams":"CNMCEKVBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"4ObSAa2jREM"},"removeLikeParams":"Cg0KCzRPYlNBYTJqUkVNGAAqDAjVjZjLBhCOy_v7AQ%3D%3D"}}}]}},"accessibilityText":"이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNMCEKVBIhMI9tH87ZCIkgMV1kE4BR28HRVm","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CMkCELW0CRgAIhMI9tH87ZCIkgMV1kE4BR28HRVm","isTogglingDisabled":true}},"likeStatusEntityKey":"Egs0T2JTQWEyalJFTSA-KAE%3D","likeStatusEntity":{"key":"Egs0T2JTQWEyalJFTSA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNECEKiPCSITCPbR_O2QiJIDFdZBOAUdvB0VZg=="}},{"innertubeCommand":{"clickTrackingParams":"CNECEKiPCSITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNICEPmGBCITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNICEPmGBCITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"4ObSAa2jREM"},"dislikeParams":"Cg0KCzRPYlNBYTJqUkVNEAAiDAjVjZjLBhDWsv37AQ%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CNICEPmGBCITCPbR_O2QiJIDFdZBOAUdvB0VZg=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNECEKiPCSITCPbR_O2QiJIDFdZBOAUdvB0VZg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNACEKiPCSITCPbR_O2QiJIDFdZBOAUdvB0VZg=="}},{"innertubeCommand":{"clickTrackingParams":"CNACEKiPCSITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"4ObSAa2jREM"},"removeLikeParams":"Cg0KCzRPYlNBYTJqUkVNGAAqDAjVjZjLBhDu0v37AQ%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNACEKiPCSITCPbR_O2QiJIDFdZBOAUdvB0VZg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CMkCELW0CRgAIhMI9tH87ZCIkgMV1kE4BR28HRVm","isTogglingDisabled":true}},"dislikeEntityKey":"Egs0T2JTQWEyalJFTSA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"Egs0T2JTQWEyalJFTSD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CM4CEOWWARgDIhMI9tH87ZCIkgMV1kE4BR28HRVm"}},{"innertubeCommand":{"clickTrackingParams":"CM4CEOWWARgDIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgs0T2JTQWEyalJFTaABAQ%3D%3D","commands":[{"clickTrackingParams":"CM4CEOWWARgDIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CM8CEI5iIhMI9tH87ZCIkgMV1kE4BR28HRVm","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CM4CEOWWARgDIhMI9tH87ZCIkgMV1kE4BR28HRVm","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CMwCEOuQCSITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CM0CEPuGBCITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D4ObSAa2jREM\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CM0CEPuGBCITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CM0CEPuGBCITCPbR_O2QiJIDFdZBOAUdvB0VZg=="}}}}}},"trackingParams":"CMwCEOuQCSITCPbR_O2QiJIDFdZBOAUdvB0VZg=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMoCEOuQCSITCPbR_O2QiJIDFdZBOAUdvB0VZg=="}},{"innertubeCommand":{"clickTrackingParams":"CMoCEOuQCSITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMsCEPuGBCITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D4ObSAa2jREM\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMsCEPuGBCITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CMsCEPuGBCITCPbR_O2QiJIDFdZBOAUdvB0VZg=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMoCEOuQCSITCPbR_O2QiJIDFdZBOAUdvB0VZg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CMkCELW0CRgAIhMI9tH87ZCIkgMV1kE4BR28HRVm","superTitleLink":{"runs":[{"text":"The Agile in Action Podcast with Bill Raymond","navigationEndpoint":{"clickTrackingParams":"CMkCELW0CRgAIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLWzwUIYZpnJsGnFUCmugOjrxYFOFNF93B","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLWzwUIYZpnJsGnFUCmugOjrxYFOFNF93B"}}}]},"dateText":{"simpleText":"2023. 12. 12."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"2년 전"}},"simpleText":"2년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Bill Raymond","navigationEndpoint":{"clickTrackingParams":"CMgCEOE5IhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/@bill-raymond","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCo63gWfWRfEciJ98mJLIU0Q","canonicalBaseUrl":"/@bill-raymond"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CMgCEOE5IhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/@bill-raymond","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCo63gWfWRfEciJ98mJLIU0Q","canonicalBaseUrl":"/@bill-raymond"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 7.01천명"}},"simpleText":"구독자 7.01천명"},"trackingParams":"CMgCEOE5IhMI9tH87ZCIkgMV1kE4BR28HRVm"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCo63gWfWRfEciJ98mJLIU0Q","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CLkCEJsrIhMI9tH87ZCIkgMV1kE4BR28HRVmKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Bill Raymond을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Bill Raymond을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CMcCEPBbIhMI9tH87ZCIkgMV1kE4BR28HRVm","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CMYCEPBbIhMI9tH87ZCIkgMV1kE4BR28HRVm","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CL8CEJf5ASITCPbR_O2QiJIDFdZBOAUdvB0VZg==","command":{"clickTrackingParams":"CL8CEJf5ASITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CL8CEJf5ASITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CMUCEOy1BBgDIhMI9tH87ZCIkgMV1kE4BR28HRVmMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQRUkHnc","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ282M2dXZldSZkVjaUo5OG1KTElVMFESAggBGAAgBFITCgIIAxILNE9iU0FhMmpSRU0YAA%3D%3D"}},"trackingParams":"CMUCEOy1BBgDIhMI9tH87ZCIkgMV1kE4BR28HRVm","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CMQCEO21BBgEIhMI9tH87ZCIkgMV1kE4BR28HRVmMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQRUkHnc","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ282M2dXZldSZkVjaUo5OG1KTElVMFESAggDGAAgBFITCgIIAxILNE9iU0FhMmpSRU0YAA%3D%3D"}},"trackingParams":"CMQCEO21BBgEIhMI9tH87ZCIkgMV1kE4BR28HRVm","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CMACENuLChgFIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMACENuLChgFIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CMECEMY4IhMI9tH87ZCIkgMV1kE4BR28HRVm","dialogMessages":[{"runs":[{"text":"Bill Raymond"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CMMCEPBbIhMI9tH87ZCIkgMV1kE4BR28HRVmMgV3YXRjaMoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"CgIIAxILNE9iU0FhMmpSRU0YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CMMCEPBbIhMI9tH87ZCIkgMV1kE4BR28HRVm"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CMICEPBbIhMI9tH87ZCIkgMV1kE4BR28HRVm"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CMACENuLChgFIhMI9tH87ZCIkgMV1kE4BR28HRVm"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CLkCEJsrIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CL4CEP2GBCITCPbR_O2QiJIDFdZBOAUdvB0VZjIJc3Vic2NyaWJlygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D4ObSAa2jREM%26continue_action%3DQUFFLUhqbWd1bE1MV1BNV3NXbkstNnB4RGhiemRldHlrUXxBQ3Jtc0tsQ1BJYjRSelZXbGw5S0RxbnA0OWptaUY3ZUVnWHBsWXRJb0h6UUMzLWpSREJxTUVuV3Mya0dkMWRPWVUxc2lXLUl3X3RjdzA0cloyY3dDbzRaM282TjdNcXkzMDN1UENGaVpETEduZHJELV82Xy10bkkwUG5mNzV2NUR0R1JFcEg1RnVKcWpHZTZjMGJLOGJtZXpmMzJHeTBJNGQxVEw2NktXT2hxeklSRE5MaTE2V19oRFktZnpuSW55a3MxcWFIVkVmOWk\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CL4CEP2GBCITCPbR_O2QiJIDFdZBOAUdvB0VZsoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbWd1bE1MV1BNV3NXbkstNnB4RGhiemRldHlrUXxBQ3Jtc0tsQ1BJYjRSelZXbGw5S0RxbnA0OWptaUY3ZUVnWHBsWXRJb0h6UUMzLWpSREJxTUVuV3Mya0dkMWRPWVUxc2lXLUl3X3RjdzA0cloyY3dDbzRaM282TjdNcXkzMDN1UENGaVpETEduZHJELV82Xy10bkkwUG5mNzV2NUR0R1JFcEg1RnVKcWpHZTZjMGJLOGJtZXpmMzJHeTBJNGQxVEw2NktXT2hxeklSRE5MaTE2V19oRFktZnpuSW55a3MxcWFIVkVmOWk","idamTag":"66429"}},"trackingParams":"CL4CEP2GBCITCPbR_O2QiJIDFdZBOAUdvB0VZg=="}}}}}},"subscribedEntityKey":"EhhVQ282M2dXZldSZkVjaUo5OG1KTElVMFEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CLkCEJsrIhMI9tH87ZCIkgMV1kE4BR28HRVmKPgdMgV3YXRjaMoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"EgIIAxgAIgs0T2JTQWEyalJFTQ%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CLkCEJsrIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CLkCEJsrIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CLsCEMY4IhMI9tH87ZCIkgMV1kE4BR28HRVm","dialogMessages":[{"runs":[{"text":"Bill Raymond"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CL0CEPBbIhMI9tH87ZCIkgMV1kE4BR28HRVmKPgdMgV3YXRjaMoBBFSQedw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"CgIIAxILNE9iU0FhMmpSRU0YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CL0CEPBbIhMI9tH87ZCIkgMV1kE4BR28HRVm"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CLwCEPBbIhMI9tH87ZCIkgMV1kE4BR28HRVm"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}],"timedAnimationData":{"animationTiming":[2498359],"macroMarkersIndex":[0],"animationDurationSecs":1.5,"borderStrokeThicknessDp":2,"borderOpacity":1,"fillOpacity":0,"trackingParams":"CLoCEPBbIhMI9tH87ZCIkgMV1kE4BR28HRVm","animationOrigin":"ANIMATION_ORIGIN_SMARTIMATION"}}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVm"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVm","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Jack Skeels, CEO of AgencyAgile, shares valuable insights on agile leadership in the Agile in Action with Bill Raymond Podcast. Jack discusses the transformative power of teams and productivity through the lens of his new book, \"UNMANAGED.\"\n\nBill and Jack discuss the hidden costs of management and how a manager can focus their role on growth and empowering teams.\n\n✅ How to embrace \"Unmanagement,\" redefine traditional management, and boost team autonomy and creativity\n✅ The cost of management by recognizing how over-management can hinder productivity\n✅ How you can empower teams by encouraging self-management for better problem-solving and efficiency\n🎉 Communication methods to prevent misunderstandings and project delays\n\nFor links related to this podcast, the full transcription, and more, visit the Agile in Action website:\nhttps://agileinaction.com/agile-in-ac...\n\nChapters:\n\n00:00 Introduction and Guest Background\n01:37 Understanding Agile and Agility\n04:14 The Cost of Management\n07:40 The Concept of UNMANAGED\n10:38 The Role of a Manager\n29:58 The Unmanager's Manifesto\n33:37 Actionable Steps for Managers\n39:49 Conclusion and Contact Information","commandRuns":[{"startIndex":835,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmSMOIje2awLTz4AHKAQRUkHnc","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbk5xNXNGTDdNbEhYdHFXMkZyczNIMjVaTHNiUXxBQ3Jtc0ttZ2FMeGE5cWNzYkJYYVY4QTBoTWlTaEM1eTlha1FIalBCclptLXdwV3UtLVZpTHpFWEs4WnRId3BUYTVTdDg0alRxS3JQWllqSU5BRGxhZElEd3Z3cmlKdDkwcnp4d1lLdlZpNy1BODhkSXlrX20tWQ\u0026q=https%3A%2F%2Fagileinaction.com%2Fagile-in-action-podcast%2F2023%2F12%2F12%2Fbecoming-a-great-un-manager.html\u0026v=4ObSAa2jREM","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbk5xNXNGTDdNbEhYdHFXMkZyczNIMjVaTHNiUXxBQ3Jtc0ttZ2FMeGE5cWNzYkJYYVY4QTBoTWlTaEM1eTlha1FIalBCclptLXdwV3UtLVZpTHpFWEs4WnRId3BUYTVTdDg0alRxS3JQWllqSU5BRGxhZElEd3Z3cmlKdDkwcnp4d1lLdlZpNy1BODhkSXlrX20tWQ\u0026q=https%3A%2F%2Fagileinaction.com%2Fagile-in-action-podcast%2F2023%2F12%2F12%2Fbecoming-a-great-un-manager.html\u0026v=4ObSAa2jREM","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":888,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","continuePlayback":true,"startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"0초"}}},{"startIndex":928,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM\u0026t=97s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","continuePlayback":true,"startTimeSeconds":97,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026osts=97\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"1분 37초"}}},{"startIndex":966,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM\u0026t=254s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","continuePlayback":true,"startTimeSeconds":254,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026osts=254\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"4분 14초"}}},{"startIndex":995,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM\u0026t=460s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","continuePlayback":true,"startTimeSeconds":460,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026osts=460\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"7분 40초"}}},{"startIndex":1026,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM\u0026t=638s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","continuePlayback":true,"startTimeSeconds":638,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026osts=638\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"10분 38초"}}},{"startIndex":1054,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM\u0026t=1798s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","continuePlayback":true,"startTimeSeconds":1798,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026osts=1798\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"29분 58초"}}},{"startIndex":1086,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM\u0026t=2017s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","continuePlayback":true,"startTimeSeconds":2017,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026osts=2017\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"33분 37초"}}},{"startIndex":1122,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMI9tH87ZCIkgMV1kE4BR28HRVmygEEVJB53A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4ObSAa2jREM\u0026t=2389s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4ObSAa2jREM","continuePlayback":true,"startTimeSeconds":2389,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e0e6d201ada34443\u0026ip=1.208.108.242\u0026osts=2389\u0026initcwndbps=4533750\u0026mt=1768293891\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"39분 49초"}}}],"styleRuns":[{"startIndex":0,"length":835,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":835,"length":40,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":875,"length":13,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":888,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":893,"length":35,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":928,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":933,"length":33,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":966,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":971,"length":24,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":995,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1000,"length":26,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1026,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1031,"length":23,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1054,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1059,"length":27,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1086,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1091,"length":31,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1122,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1127,"length":35,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":835,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":835,"length":40,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":875,"length":13,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":888,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":893,"length":35,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":928,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":933,"length":33,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":966,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":971,"length":24,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":995,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1000,"length":26,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1026,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1031,"length":23,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1054,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1059,"length":27,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1086,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1091,"length":31,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1122,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1127,"length":35,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CLcCELsvGAMiEwj20fztkIiSAxXWQTgFHbwdFWbKAQRUkHnc","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/next"}},"continuationCommand":{"token":"Eg0SCzRPYlNBYTJqUkVNGAYyJSIRIgs0T2JTQWEyalJFTTAAeAJCEGNvbW1lbnRzLXNlY3Rpb24%3D","request":"CONTINUATION_REQUEST_TYPE_WATCH_NEXT"}}}}],"trackingParams":"CLcCELsvGAMiEwj20fztkIiSAxXWQTgFHbwdFWY=","sectionIdentifier":"comment-item-section","targetId":"comments-section"}}],"trackingParams":"CLYCELovIhMI9tH87ZCIkgMV1kE4BR28HRVm"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/z8J4KM_HCHQ/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLAvwaoEwIyc8otBsDxWyuBD0htb6w","width":168,"height":94},{"url":"https://i.ytimg.com/vi/z8J4KM_HCHQ/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDCZsrlzJJGzSacrj87egDEK1zS9Q","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"22:49","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"z8J4KM_HCHQ","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedT | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/user-preferences#how-preferences-are-determined | User Preferences - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences User Preferences Tenant Preferences Preference Evaluation Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Preferences User Preferences Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Preferences User Preferences OpenAI Open in ChatGPT Learn how user preferences work in SuprSend and how to capture them. OpenAI Open in ChatGPT Before you start: Make sure you’ve set up notification categories first. See Manage Categories and Preferences for step-by-step instructions. Preferences let users control which notifications they receive. Instead of an all-or-nothing approach, users can opt out of specific categories, choose preferred channels, and set notification frequency. This granular control reduces the chance that users disable all notifications from your platform. In SuprSend, you can use ready-made UI and APIs to manage multi-tenant preference use cases. This includes letting admins set preferences for internal teams and handle notifications for enterprise customers, where companies, customers, and end users have distinct preferences. How It Works Preferences are evaluated in priority order: User Preference → Tenant Default → Category Default Three Levels of Control Global channel opt-outs, category preferences, and channel opt-outs within categories What are user preferences? Preferences only work with sub-categories: User preferences apply to sub-categories you create, not root-categories (System, Transactional, Promotional). Use sub-category slugs in workflows for preferences to work. Each user has a preference set that controls which notifications they receive. A preference set has three levels of control: channel_preferences — Global channel opt-outs (e.g., opt out of all email) categories — Category-level preferences (opt in/out of all channels of a notification type) opt_out_channels — Opt-in/out of specific channels within a category Example: Copy Ask AI { "channel_preferences" : [ { "channel" : "email" , "is_restricted" : true } ], "categories" : [ { "category" : "invoice-ready" , "preference" : "opt_out" }, { "category" : "payment-reminder" , "preference" : "opt_in" , "opt_out_channels" : [ "slack" ] } ] } In this example: user opted out of email globally, opted out of invoice-ready category completely, and stays opted in to payment-reminder but without Slack. How preferences are determined When a user hasn’t set their own preferences in a category, SuprSend uses defaults in this order: User Preference — Individual user’s explicit choices (highest priority) Tenant Default Preference — Default preferences set by tenant for the category Category Default Preference — Default preferences set at the category level (lowest priority) Preference precedence: User Preference → Tenant Default Preference → Category Default Preference Preference precedence is determined at category level . So, if a user overrides preference for a category but doesn’t touch other categories, defaults continue to apply to the untouched categories. Setting up preference categories Before users can set their preferences, you must first create and configure preference categories. For step-by-step setup instructions, see Manage Categories and Preferences . Default preferences Default preferences determine how users receive notifications when they haven’t set their own preferences. Configure these at the sub-category level when setting up categories. What default preferences control Default preferences control: Channel or Category defaults : Which categories or channels will be turned on/off by default on users’ preference page. Mandatory channels : Which channel or category users cannot opt out of (shown as disabled on preference page) Visibility : Whether a category appears on the preference page Preference types On — Users receive this category's notifications by default Users will receive notifications in this category by default. You can configure Opt-in Channels to specify which channels are included in the default “On” state: All : All available channels are enabled by default Selected Channels only : Only specific channels you select are enabled by default (e.g., Email, Android Push, iOS Push, In-App Inbox, MS Teams, Slack) Off — Users must opt in to get notifications Users will not receive notifications unless they change the preference. Can't Unsubscribe — Users cannot opt out of mandatory channels in this category Prevents users from fully opting out of the category. When selected, you can configure: Mandatory Channels : Channels which can’t be opted out of by the user. Set to “All” or “Selected Channels”. Opt-in Channels : In case of “Selected” Mandatory Channels, you can configure the channels that will be opted in by default. Channels other than mandatory and opt-in will be skipped for sending notification unless user explicitly opts in to them. Even when a category is set to “Can’t Unsubscribe,” users can still control channel-level preferences if your channel-level settings allow it. This configuration gives you fine-grained control over which channels a user is opted into by default, letting you differentiate between must-deliver channels, default-on channels, and optional channels. Capturing user preferences Users can set their preferences through one of the following methods: Hosted preference page Once you publish preference categories, SuprSend automatically generates a dedicated unsubscription webpage for collecting user preferences . Users can set channel-specific preferences from the hosted page. If the link is included in an email, the hosted page will show and save email preferences. Include it in your templates using {{$hosted_preference_url}} . This page is currently hosted on a SuprSend domain, but you can reach out to [email protected] if you’d prefer it hosted on your own domain. Embed in your product You can embed the preference interface directly inside your product using SuprSend’s ready-made UI components. SDKs exist in the languages below. Update your product preference page link on the tenant page and render it in templates using {{$embedded_preference_url}} . Javascript React Angular Embeddable preference page Controlling what categories to show on UI It’s always a good practice to show only the categories that are relevant to the user. There are two ways to achieve this: Hide categories for tenant users In a multi-tenant setup, tenants or admins can control which categories their users see. Setting visible_to_subscriber: false in tenant preferences hides the category from tenant users’ preference pages. Hidden categories won’t send notifications to those users, even if they previously opted in. Filter categories with tags Use tags to show categories based on user roles, departments, or teams. Filter categories in the preference center using the tags query parameter. 1 Setting Preference tags Tags can be added to sections and sub-categories directly from Developers → Notification Categories in the SuprSend Console. When a tag is assigned at the section level, it automatically applies to all categories under that section—so filtering by a section tag also filters its child categories. 2 Filter Categories with Tags You can filter categories using the tags query parameter in the API. This can be a simple tag match (e.g. tags=tag1 ) or a more advanced filter using logical operators. Supported operators: Operator Operand Datatype Description Example exists boolean Returns categories where any tag is set tags={ "exists": true } not string Excludes categories that have the specified tag tags={ "not": "admin" } or array Returns categories that match any of the provided tags tags={ "or": ["sales", "marketing"] } and array Returns categories that match all provided tags tags={ "and": ["sales", "manager"] } You can combine these operators for nested filtering like tags={ "or": [{ "and": ["sales", "manager"] }, { "and": ["marketing", "associate"] }] } . If no tags are provided, the preference center returns all visible categories. For details on how tags work, see Tags . Translating preference categories in user’s locale Upload translation files for your category names and descriptions. See How to manage Category translations for details. Once uploaded, pass a locale parameter (e.g., es , fr , de ) when: Loading the embeddable preference center As a query parameter in the get user preference API . The hosted preference page picks the locale from user’s profile. On hosted preference page, Dynamic content (category names, descriptions) is translated using translation files you upload. Static content (CTA text, labels, buttons, etc.) is translated automatically using SuprSend’s built-in i18n support for commonly used languages. You can see the list of supported languages below. Supported languages Language Code English en Spanish es French fr German de Italian it Portuguese pt Catalan ca Russian ru Dutch nl Polish pl Japanese ja Vietnamese vi Language Code Indonesian id Korean ko Serbian sr Norwegian no Hebrew he Chinese zh Finnish fi Swedish sv Czech cs Lithuanian lt Arabic ar How preferences are evaluated SuprSend evaluates user preferences at send time. For every recipient, the system checks user-level preferences first, then tenant-level overrides, and finally category defaults. For detailed information on the evaluation process, see Preference Evaluation . Other ways to unsubcribe from notifications In addition to the preference center within SuprSend, communication channels provide their own opt-out options, which SuprSend manages internally. Email: Unsubscribe URL header Gmail requires an unsubscribe URL in email headers when sending bulk emails (5,000+ emails/day). Most email providers expect you to add your own unsubscription page or offer a basic all-or-nothing opt-out option. You can add {{$hosted_preference_url}} here to load the SuprSend hosted preference page from the email header. Inbox (In-App): Render preference page inside your Inbox Companies also give users the option to load preference settings inside their in-app Inbox or provide a link to redirect users to the Preference center in their product. Mobile Push: Preference Page in App settings For mobile push notifications, users typically manage their preferences through the app settings. The category you assign in your workflow is also sent as the push “category” (used by Android/iOS to group notifications). If you set preference categories, the system automatically reflects them in the user’s app settings, loading similar preference controls. SMS & Whatsapp: Reply `STOP` Users generally unsubscribe from Short Message Service (SMS) by replying “STOP.” SuprSend automatically marks the SMS channel as inactive in the user’s profile when it receives a STOP reply. For WhatsApp, opt-out behavior depends on the provider; where supported, users can reply STOP and SuprSend will mark the channel inactive. FAQ How do I set up a digest schedule? You can create sub-categories for different digest schedules or set the digest schedule in the user profile and pass a dynamic schedule in the workflow digest node. An option to set the digest schedule directly on your preference page will be available soon. I have a use case where a company has multiple departments/roles, and the admin will set preferences for users in these departments. You can manage this with tenant preferences. In the SuprSend system, each tenant represents an organization, and the administrator sets which categories to send to their internal team using the tenant preference API . What happens to existing user preference view if I change default preference setting? Changing the default preference for a category doesn’t affect users who have already made changes to that category. For categories where users haven’t made any changes, the preferences update according to the new default settings. I have multiple enterprise customers with various product offerings. Customers should only receive notifications for the products they have enabled, and the same should be visible on their preference page. How can I manage this in SuprSend? You can turn off categories for tenants from the tenant page on the SuprSend console. Turning off the preference for a category automatically removes it from the tenant preference APIs and UI view. To further apply this to the tenant’s users, set visible to subscriber to false in the default tenant preferences to hide the category from the tenant’s end users. Why don't I see the 'inbox' channel in my user preferences? The inbox channel preference is behind a feature flag and needs to be enabled for your account. If you don’t see the inbox channel in your user preferences, contact [email protected] to have the feature flag enabled for your workspace. Why do users still receive promotional notifications even after unsubscribing from all categories? Unsubscribing from top-level categories (System, Transactional, Promotional) is not supported . Preferences only work with sub-categories you create. If you’re sending notifications using a top-level category like "promotional" in your workflows, users cannot unsubscribe from those notifications through the preference center, even if they unsubscribe from all visible categories. Solution: Create sub-categories under the Promotional category (e.g., “Marketing”, “Newsletter”, “Product Updates”) and use those sub-category slugs in your workflows instead of the top-level category. This allows users to: See and control preferences for each notification type Opt out of specific sub-categories Have their preferences respected when you send notifications Best practice: Organize notifications into meaningful sub-categories rather than using top-level categories directly. This provides users with granular control and improves their experience. Can I use user preferences in workflow branching to control which notifications are sent? User preferences are not passed in the workflow payload, so you cannot directly access them in branch conditions or other workflow nodes. Workaround: If you need to use preference-based logic in workflows (e.g., to route notifications based on user preferences or combine multiple notification scenarios in a single workflow), you can: Store the same preference data as custom properties in the user profile Use those custom properties in branch conditions to route notifications Example use case: If you want to combine multiple notification scenarios (e.g., “New Comment”, “Reply on my comment”, “I am mentioned”) in a single workflow to avoid duplicate notifications, you can: Store user preferences for each scenario as custom properties (e.g., wants_new_comment_notifications: true , wants_mention_notifications: true ) Use branch conditions to check these properties and route notifications accordingly This allows you to have one workflow that handles all scenarios while respecting user preferences Alternative approach: Create separate workflows for each notification scenario with conditions in the Trigger node. Each workflow can use its own preference category, allowing users to control each scenario independently. How do I let users control both notification on/off and the time they want to be reminded (e.g., medicine reminders)? You can combine preference categories with dynamic digest schedules to achieve this: 1. Set up preference categories: Create a preference category (e.g., “medicine-reminders”) that users can opt in/out of using the preference APIs or preference center UI . 2. Store time preference as user property: When users select their preferred reminder time, store it as a custom property in their user profile. For example: Copy Ask AI user.set({ "medicineReminderTime" : { "frequency" : "daily" , "time" : "09:00" , "tz_selection" : "recipient" } }) 3. Use dynamic schedule in digest node: In your workflow’s digest node, configure it to use a dynamic schedule that references the user property (e.g., ."$recipient".medicineReminderTime ). The digest will only send if the user has opted in to the category, and it will send at their preferred time. Implementation flow: Client side (React Native) : Capture user’s time preference and call your backend API Server side (Supabase Edge Function) : Update both the user’s preference (opt in/out) via SuprSend preference API and store the time preference as a user property Workflow : Use preference category to control on/off, and dynamic schedule to control timing For detailed information, see Dynamic Schedule in the digest documentation. Related documentation Notification Categories - Setting up categories & defaults Manage Categories and Preferences - Complete guide to setting up and managing categories and preferences Tenant Preferences - Managing tenant-level preferences Preference Evaluation - How SuprSend evaluates preferences at runtime Was this page helpful? Yes No Suggest edits Raise issue Previous Tenant Preferences Learn how to manage preferences for your tenants and their users. Next ⌘ I x github linkedin youtube Powered by On this page What are user preferences? How preferences are determined Setting up preference categories Default preferences What default preferences control Preference types Capturing user preferences Hosted preference page Embed in your product Controlling what categories to show on UI Hide categories for tenant users Filter categories with tags Translating preference categories in user’s locale How preferences are evaluated Other ways to unsubcribe from notifications FAQ Related documentation | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference | HTML reference - HTML | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTML Reference Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) HTML reference This HTML reference describes all elements and attributes of HTML, including global attributes that apply to all elements. HTML element reference This page lists all the HTML elements, which are created using tags. HTML attribute reference Elements in HTML have attributes; these are additional values that configure the elements or adjust their behavior in various ways to meet the criteria the users want. Global attributes Global attributes are attributes common to all HTML elements; they can be used on all elements, though they may have no effect on some elements. Content categories Every HTML element is a member of one or more content categories — these categories group elements that share common characteristics. HTML comments HTML comments are used to add explanatory notes to the markup or to prevent the browser from interpreting specific parts of the document. Date and time formats used in HTML Certain HTML elements allow you to specify dates and/or times as the value or as the value of an attribute. These include the date and time variations of the <input> element as well as the <ins> and <del> elements. Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jul 9, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTML Guides Cheatsheet Comments Constraint validation Content categories Date and time formats Microdata Microformats Quirks and standards modes Responsive images How to Define terms with HTML Use data attributes Use cross-origin images Add a hitmap on top of an image Author fast-loading HTML pages Add JavaScript Reference Elements <a> <abbr> <acronym> Deprecated <address> <area> <article> <aside> <audio> <b> <base> <bdi> <bdo> <big> Deprecated <blockquote> <body> <br> <button> <canvas> <caption> <center> Deprecated <cite> <code> <col> <colgroup> <data> <datalist> <dd> <del> <details> <dfn> <dialog> <dir> Deprecated <div> <dl> <dt> <em> <embed> <fencedframe> Experimental <fieldset> <figcaption> <figure> <font> Deprecated <footer> <form> <frame> Deprecated <frameset> Deprecated <h1> <head> <header> <hgroup> <hr> <html> <i> <iframe> <img> <input> <ins> <kbd> <label> <legend> <li> <link> <main> <map> <mark> <marquee> Deprecated <menu> <meta> <meter> <nav> <nobr> Deprecated <noembed> Deprecated <noframes> Deprecated <noscript> <object> <ol> <optgroup> <option> <output> <p> <param> Deprecated <picture> <plaintext> Deprecated <pre> <progress> <q> <rb> Deprecated <rp> <rt> <rtc> Deprecated <ruby> <s> <samp> <script> <search> <section> <select> <selectedcontent> Experimental <slot> <small> <source> <span> <strike> Deprecated <strong> <style> <sub> <summary> <sup> <table> <tbody> <td> <template> <textarea> <tfoot> <th> <thead> <time> <title> <tr> <track> <tt> Deprecated <u> <ul> <var> <video> <wbr> <xmp> Deprecated Attributes accept autocomplete capture content crossorigin dirname disabled elementtiming fetchpriority for form max maxlength min minlength multiple pattern placeholder readonly rel required size step Global attributes accesskey anchor Experimental Non-standard autocapitalize autocorrect autofocus class contenteditable data-* dir draggable enterkeyhint exportparts hidden id inert inputmode is itemid itemprop itemref itemscope itemtype lang nonce part popover slot spellcheck style tabindex title translate virtualkeyboardpolicy Experimental writingsuggestions Attributes by element <input> type <input type="button"> <input type="checkbox"> <input type="color"> <input type="date"> <input type="datetime-local"> <input type="email"> <input type="file"> <input type="hidden"> <input type="image"> <input type="month"> <input type="number"> <input type="password"> <input type="radio"> <input type="range"> <input type="reset"> <input type="search"> <input type="submit"> <input type="tel"> <input type="text"> <input type="time"> <input type="url"> <input type="week"> <script> type importmap speculationrules Experimental <meta> name color-scheme referrer robots theme-color viewport <meta> http-equiv Attribute values rel keywords rel="alternate stylesheet" rel="compression-dictionary" Experimental rel="dns-prefetch" rel="manifest" rel="me" rel="modulepreload" rel="noopener" rel="noreferrer" rel="preconnect" rel="prefetch" rel="preload" rel="prerender" Non-standard Deprecated Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/HTML/Guides/Responsive_images | Using responsive images in HTML - HTML | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTML Guides Responsive images Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) Using responsive images in HTML In this article, we'll learn about the concept of responsive images — images that work well on devices with widely differing screen sizes, resolutions, and other such features — and look at what tools HTML provides to help implement them. This helps to improve performance across different devices. In this article Why responsive images? How do you create responsive images? Implementing your own responsive images Summary See also Why responsive images? Let's examine a typical scenario. A typical website may contain a header image and some content images below the header. The header image will likely span the whole of the width of the header, and the content image will fit somewhere inside the content column. Here's an example: This works well on a wide screen device, such as a laptop or desktop (you can see the example live and find the source code on GitHub.) We won't discuss the CSS much in this lesson, except to say that: The body content has been set to a maximum width of 1200 pixels — in viewports above that width, the body remains at 1200px and centers itself in the available space. In viewports below that width, the body will stay at 100% of the width of the viewport. The header image has been set so that its center always stays in the center of the header, no matter what width the heading is set at. If the site is being viewed on a narrower screen, the important detail in the center of the image (the people) can still be seen, and the excess is lost off either side. It is 200px high. The content images have been set so that if the body element becomes smaller than the image, the images start to shrink so that they always stay inside the body, rather than overflowing it. However, issues arise when you start to view the site on a narrow screen device. The header below looks OK, but it's starting to take up a lot of the screen height for a mobile device. And at this size, it is difficult to see faces of the two people within the first content image. An improvement would be to display a cropped version of the image which displays the important details of the image when the site is viewed on a narrow screen. A second cropped image could be displayed for a medium-width screen device, like a tablet. The general problem whereby you want to serve different cropped images in that way, for various layouts, is commonly known as the art direction problem . In addition, there is no need to embed such large images on the page if it is being viewed on a mobile screen. Doing so can waste bandwidth; in particular, mobile users don't want to waste bandwidth by downloading a large image intended for desktop users, when a small image would do for their device. Conversely, a small raster image starts to look grainy when displayed larger than its original size (a raster image is a set number of pixels wide and a set number of pixels tall). Ideally, multiple resolutions would be made available to the user's web browser. The browser could then determine the optimal resolution to load based on the screen size of the user's device. This is called the resolution switching problem . To make things more complicated, some devices have high resolution screens that need larger images than you might expect to display nicely. This is essentially the same problem, but in a slightly different context. You might think that vector images would solve these problems, and they do to a certain degree — they are small in file size and scale well, and you should use them wherever possible. However, they aren't suitable for all image types. Vector images are great for simple graphics, patterns, interface elements, etc., but it starts to get very complex to create a vector-based image with the kind of detail that you'd find in say, a photo. Raster image formats such as JPEGs are more suited to the kind of images we see in the above example. This kind of problem didn't exist when the web first existed, in the early to mid 90s — back then the only devices in existence to browse the Web were desktops and laptops, so browser engineers and spec writers didn't even think to implement solutions. Responsive image technologies were implemented recently to solve the problems indicated above by letting you offer the browser several image files, either all showing the same thing but containing different numbers of pixels ( resolution switching ), or different images suitable for different space allocations ( art direction ). Note: The new features discussed in this article — srcset / sizes / <picture> — are all supported in modern desktop and mobile browsers. How do you create responsive images? In this section, we'll look at the two problems illustrated above and show how to solve them using HTML's responsive image features. You should note that we will be focusing on <img> elements for this section, as seen in the content area of the example above — the image in the site header is only for decoration, and therefore implemented using CSS background images. CSS arguably has better tools for responsive design than HTML, and we'll talk about those in a future CSS module. Resolution switching: Different sizes So, what is the problem that we want to solve with resolution switching? We want to display identical image content, just larger or smaller depending on the device — this is the situation we have with the second content image in our example. The standard <img> element traditionally only lets you point the browser to a single source file: html <img src="elva-fairy-800w.jpg" alt="Elva dressed as a fairy" /> We can however use two attributes — srcset and sizes — to provide several additional source images along with hints to help the browser pick the right one. You can see an example of this in our responsive.html example on GitHub (see also the source code ): html <img srcset="elva-fairy-480w.jpg 480w, elva-fairy-800w.jpg 800w" sizes="(width <= 600px) 480px, 800px" src="elva-fairy-800w.jpg" alt="Elva dressed as a fairy" /> The srcset and sizes attributes look complicated, but they're not too hard to understand if you format them as shown above, with a different part of the attribute value on each line. Each value contains a comma-separated list, and each part of those lists is made up of three sub-parts. Let's run through the contents of each now: srcset defines the set of images we will allow the browser to choose between, and what size each image is. Each set of image information is separated from the previous one by a comma. For each one, we write: An image filename ( elva-fairy-480w.jpg ) A space The image's intrinsic width in pixels ( 480w ) — note that this uses the w unit, not px as you might expect. An image's intrinsic size is its real size, which can be found by inspecting the image file on your computer (for example, on a Mac you can select the image in Finder and press Cmd + I to bring up the info screen). sizes defines a set of media conditions (e.g., screen widths) and indicates what image size would be best to choose, when certain media conditions are true — these are the hints we talked about earlier. In this case, before each comma we write: A media condition ( (width <= 600px) ) — you'll learn more about these in the CSS topic , but for now let's just say that a media condition describes a possible state that the screen can be in. In this case, we are saying "when the viewport width is 600 pixels or less". A space The width of the slot the image will fill when the media condition is true ( 480px ) Note: In sizes , you can use any length value . For example, rather than providing an absolute width (for example, 480px ), you can alternatively provide a width relative to the viewport (for example, 50vw ). However, you cannot use a percentage as the slot width. You may have noticed that the last slot width has no media condition (this is the default that is chosen when none of the media conditions are true). The browser ignores everything after the first matching condition, so be careful how you order the media conditions. So, with these attributes in place, the browser will: Look at screen size, pixel density, zoom level, screen orientation, and network speed. Work out which media condition in the sizes list is the first one to be true. Look at the slot size given to that media query. Load the image referenced in the srcset list that has the same size as the slot. If there isn't an exact match for the display size, the browser will choose the first image that is bigger than the chosen slot size and scale it down to fit. And that's it! At this point, if a supporting browser with a viewport width of 480px loads the page, the (width <= 600px) media condition will be true, and so the browser chooses the 480px slot. The elva-fairy-480w.jpg will be loaded, as its inherent width ( 480w ) is closest to the slot size. The 800px picture is 128KB on disk, whereas the 480px version is only 63KB — a saving of 65KB. Now, imagine if this was a page that had many pictures on it. Using this technique could save mobile users a lot of bandwidth. Note: When testing this with a desktop browser, if the browser fails to load the narrower images when you've got its window set to the narrowest width, have a look at what the viewport is (you can approximate it by going into the browser's JavaScript console and typing in document.querySelector('html').clientWidth ). Different browsers have minimum sizes that they'll let you reduce the window width to, and they might be wider than you'd think. When testing it with a mobile browser, you can use tools like Firefox's about:debugging page to inspect the page loaded on the mobile using the desktop developer tools. To see which images were loaded, you can use Firefox DevTools's Network Monitor tab or Chrome DevTools's Network panel. For Chrome, you may also want to disable cache to prevent it from picking already downloaded images. Older browsers that don't support these features will just ignore them. Instead, those browsers will go ahead and load the image referenced in the src attribute as normal. Note: In the <head> of the example linked above, you'll find the line <meta name="viewport" content="width=device-width"> : this forces mobile browsers to adopt their real viewport width for loading web pages (some mobile browsers lie about their viewport width, and instead load pages at a larger viewport width then shrink the loaded page down, which is not very helpful for responsive images or design). Resolution switching: Same size, different resolutions Suppose you have an image that will be rendered at the same real-world size on displays that have different screen resolutions. You can provide a better user experience on high resolution displays by serving a higher resolution version of the image. To achieve this you can allow the browser to choose an appropriate resolution image by using srcset with x-descriptors and without sizes — a somewhat easier syntax! You can find an example of what this looks like in srcset-resolutions.html (see also the source code ): html <img srcset="elva-fairy-320w.jpg, elva-fairy-480w.jpg 1.5x, elva-fairy-640w.jpg 2x" src="elva-fairy-640w.jpg" alt="Elva dressed as a fairy" /> Note that even though the image is always displayed with the same size, on higher resolution displays you get to see more details. In this example, the following CSS is applied to the image so that it will have a width of 320 pixels on the screen (also called CSS pixels): css img { width: 320px; } In this case, sizes is not needed — the browser works out what resolution the display is that it is being shown on, and serves the most appropriate image referenced in the srcset . So if the device accessing the page has a standard/low resolution display, with one device pixel representing each CSS pixel, the elva-fairy-320w.jpg image will be loaded (the 1x is implied, so you don't need to include it.) If the device has a high resolution of two device pixels per CSS pixel or more, the elva-fairy-640w.jpg image will be loaded. The 640px image is 93KB, whereas the 320px image is only 39KB. Art direction To recap, the art direction problem involves wanting to change the image displayed to suit different image display sizes. For example, a web page includes a large landscape shot with a person in the middle when viewed on a desktop browser. When viewed on a mobile browser, that same image is shrunk down, making the person in the image very small and hard to see. It would probably be better to show a smaller, portrait image on mobile, which zooms in on the person. The <picture> element allows us to implement just this kind of solution. Returning to our original not-responsive.html example, we have an image that badly needs art direction: html <img src="elva-800w.jpg" alt="Chris standing up holding his daughter Elva" /> Let's fix this, with <picture> ! Like <video> and <audio> , the <picture> element is a wrapper containing several <source> elements that provide different sources for the browser to choose from, followed by the all-important <img> element. The code in responsive.html looks like so: html <picture> <source media="(width < 800px)" srcset="elva-480w-close-portrait.jpg" /> <source media="(width >= 800px)" srcset="elva-800w.jpg" /> <img src="elva-800w.jpg" alt="Chris standing up holding his daughter Elva" /> </picture> The <source> elements include a media attribute that contains a media condition — as with the first srcset example, these conditions are tests that decide which image is shown — the first one that returns true will be displayed. In this case, if the viewport width is less than 800px wide, the first <source> element's image will be displayed. If the viewport width is 800px or more, it'll be the second one. The srcset attributes contain the path to the image to display. Just as we saw with <img> above, <source> can take a srcset attribute with multiple images referenced, as well as a sizes attribute. So, you could offer multiple images via a <picture> element, but then also offer multiple resolutions of each one. Realistically, you probably won't want to do this kind of thing very often. In all cases, you must provide an <img> element, with src and alt , right before </picture> , otherwise no images will appear. This provides a default case that will apply when none of the media conditions return true (you could actually remove the second <source> element in this example), and a fallback for browsers that don't support the <picture> element. This code allows us to display a suitable image on both wide screen and narrow screen displays, as shown below: Note: You should use the media attribute only in art direction scenarios; when you do use media , don't also offer media conditions within the sizes attribute. Why can't we just do this using CSS or JavaScript? When the browser starts to load a page, it starts to download (preload) any images before the main parser has started to load and interpret the page's CSS and JavaScript. That mechanism is useful in general for reducing page load times, but it is not helpful for responsive images — hence the need to implement solutions like srcset . For example, you couldn't load the <img> element, then detect the viewport width with JavaScript, and then dynamically change the source image to a smaller one if desired. By then, the original image would already have been loaded, and you would load the small image as well, which is even worse in responsive image terms. Implementing your own responsive images In this exercise, we're expecting you to be brave and do it alone, mostly. We want you to implement your own suitable art-directed narrow screen/wide screenshot using <picture> , and a resolution switching example that uses srcset . Write some HTML to contain your code (use not-responsive.html as a starting point, if you like). Find a nice wide screen landscape image with some kind of detail contained in it somewhere. Create a web-sized version of it using a graphics editor, then crop it to show a smaller part that zooms in on the detail, and create a second image (about 480px wide is good for this). Use the <picture> element to implement an art direction picture switcher! Create multiple image files of different sizes, each showing the same picture. Use srcset / sizes to create a resolution switcher example, either to serve the same size image at different resolutions depending on the device resolution or to serve different image sizes depending on the viewport widths. Summary That's a wrap for responsive images — we hope you enjoyed playing with these new techniques. As a recap, there are two distinct problems we've been discussing here: Art direction : The problem whereby you want to serve cropped images for different layouts — for example a landscape image showing a full scene for a desktop layout, and a portrait image showing the main subject zoomed in for a mobile layout. You can solve this problem using the <picture> element. Resolution switching : The problem whereby you want to serve smaller image files to narrow-screen devices, as they don't need huge images like desktop displays do — and to serve different resolution images to high density/low density screens. You can solve this problem using vector graphics (SVG images) and the srcset with sizes attributes. See also Learn: Responsive design Jason Grigsby's excellent introduction to responsive images Responsive Images: If you're just changing resolutions, use srcset — includes more explanation of how the browser works out which image to use <img> <picture> <source> Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 6, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTML Guides Cheatsheet Comments Constraint validation Content categories Date and time formats Microdata Microformats Quirks and standards modes Responsive images How to Define terms with HTML Use data attributes Use cross-origin images Add a hitmap on top of an image Author fast-loading HTML pages Add JavaScript Reference Elements <a> <abbr> <acronym> Deprecated <address> <area> <article> <aside> <audio> <b> <base> <bdi> <bdo> <big> Deprecated <blockquote> <body> <br> <button> <canvas> <caption> <center> Deprecated <cite> <code> <col> <colgroup> <data> <datalist> <dd> <del> <details> <dfn> <dialog> <dir> Deprecated <div> <dl> <dt> <em> <embed> <fencedframe> Experimental <fieldset> <figcaption> <figure> <font> Deprecated <footer> <form> <frame> Deprecated <frameset> Deprecated <h1> <head> <header> <hgroup> <hr> <html> <i> <iframe> <img> <input> <ins> <kbd> <label> <legend> <li> <link> <main> <map> <mark> <marquee> Deprecated <menu> <meta> <meter> <nav> <nobr> Deprecated <noembed> Deprecated <noframes> Deprecated <noscript> <object> <ol> <optgroup> <option> <output> <p> <param> Deprecated <picture> <plaintext> Deprecated <pre> <progress> <q> <rb> Deprecated <rp> <rt> <rtc> Deprecated <ruby> <s> <samp> <script> <search> <section> <select> <selectedcontent> Experimental <slot> <small> <source> <span> <strike> Deprecated <strong> <style> <sub> <summary> <sup> <table> <tbody> <td> <template> <textarea> <tfoot> <th> <thead> <time> <title> <tr> <track> <tt> Deprecated <u> <ul> <var> <video> <wbr> <xmp> Deprecated Attributes accept autocomplete capture content crossorigin dirname disabled elementtiming fetchpriority for form max maxlength min minlength multiple pattern placeholder readonly rel required size step Global attributes accesskey anchor Experimental Non-standard autocapitalize autocorrect autofocus class contenteditable data-* dir draggable enterkeyhint exportparts hidden id inert inputmode is itemid itemprop itemref itemscope itemtype lang nonce part popover slot spellcheck style tabindex title translate virtualkeyboardpolicy Experimental writingsuggestions Attributes by element <input> type <input type="button"> <input type="checkbox"> <input type="color"> <input type="date"> <input type="datetime-local"> <input type="email"> <input type="file"> <input type="hidden"> <input type="image"> <input type="month"> <input type="number"> <input type="password"> <input type="radio"> <input type="range"> <input type="reset"> <input type="search"> <input type="submit"> <input type="tel"> <input type="text"> <input type="time"> <input type="url"> <input type="week"> <script> type importmap speculationrules Experimental <meta> name color-scheme referrer robots theme-color viewport <meta> http-equiv Attribute values rel keywords rel="alternate stylesheet" rel="compression-dictionary" Experimental rel="dns-prefetch" rel="manifest" rel="me" rel="modulepreload" rel="noopener" rel="noreferrer" rel="preconnect" rel="prefetch" rel="preload" rel="prerender" Non-standard Deprecated Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/Accessibility | Accessibility | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Accessibility Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Accessibility Accessibility (often abbreviated to A11y — as in, "a", then 11 characters, and then "y") in web development means enabling as many people as possible to use websites, even when those people's abilities are limited in some way. For many people, technology makes things easier. For people with disabilities, technology makes things possible. Accessibility means developing content to be as accessible as possible, no matter an individual's physical and cognitive abilities and how they access the web. The Web is fundamentally designed to work for all people , whatever their hardware, software, language, location, or ability. When the Web meets this goal, it is accessible to people with a diverse range of hearing, movement, sight, and cognitive ability. – ( W3C - Accessibility ) In this article Beginner's tutorials Accessibility guides References See also Beginner's tutorials Our learn web development Accessibility module contains modern, up-to-date tutorials covering accessibility fundamentals. What is accessibility? This article starts off the module with a good look at what accessibility is — this includes what groups of people we need to consider and why, what tools different people use to interact with the web, and how we can make accessibility part of our web development workflow. Accessibility tooling and assistive technology Next we turn our attention to accessibility tooling, providing information on the kinds of tools you can use to help solve accessibility issues, and the assistive technologies used by people with disabilities as they browse the web. You'll be using these tools throughout subsequent articles. HTML: A good basis for accessibility A great deal of web content can be made accessible just by making sure the correct HTML elements are always used for the correct purpose. This article looks in detail at how HTML can be used to ensure maximum accessibility. CSS and JavaScript accessibility best practices CSS and JavaScript, when used properly, also have the potential to allow for accessible web experiences, but if misused they can significantly harm accessibility. This article outlines some CSS and JavaScript best practices that should be considered to ensure that even complex content is as accessible as possible. WAI-ARIA basics Following on from the previous article, sometimes making complex UI controls that involve unsemantic HTML and dynamic JavaScript-updated content can be difficult. WAI-ARIA is a technology that can help with such problems by adding in further semantics that browsers and assistive technologies can recognize and use to let users know what is going on. Here we'll show how to use it at a basic level to improve accessibility. Accessible multimedia Another category of content that can create accessibility problems is multimedia — video, audio, and image content need to be given proper textual alternatives, so they can be understood by assistive technologies and their users. This article shows how. Mobile accessibility With web access on mobile devices being so popular, and popular platforms such as iOS and Android having fully-fledged accessibility tools, it is important to consider the accessibility of your web content on these platforms. This article looks at mobile-specific accessibility considerations. Accessibility guides The Accessibility guides cover authoring principles, WCAG compliance, accessible widgets and navigation, mobile accessibility, and other key topics that will help you understand why accessibility is crucial for the web and how to improve it in your projects. Accessibility information for web authors This document lists guidelines and regulations, how-to's, and tools for checking and repairing accessibility problems with websites. Personalization to help browse safely This article discusses making web content accessible for those with vestibular disorders, and those who support them, by taking advantage of personalization and accessibility settings built into the operating systems. Accessible web applications and widgets Most JavaScript libraries offer a library of client-side widgets that mimic the behavior of familiar desktop interfaces. While this results in a widget that looks like its desktop counterpart, there usually isn't enough semantic information in the markup to be usable by an assistive technology. This document describes techniques to improve accessibility of such widgets. Keyboard-navigable JavaScript widgets Until now, web developers who wanted to make their styled <div> and <span> based widgets accessible have lacked proper techniques. Keyboard accessibility is part of the minimum accessibility requirements, which a developer should be aware of. This document describes techniques to make JavaScript widgets accessible with the keyboard. Mobile accessibility checklist This document provides a concise checklist of accessibility requirements for mobile app developers. Understanding the Web Content Accessibility Guidelines (WCAG) A set of articles that provide quick explanations to help you understand the steps that need to be taken to conform to the recommendations outlined in the Web Content Accessibility Guidelines (WCAG). Cognitive accessibility Cognitive accessibility covers accessibility considerations for people with cognition and learning disabilities. This document introduces cognitive accessibility and improving accessibility of the web for people with cognitive and learning differences. Accessibility and spatial patterns This document describes visual patterns that can induce physical symptoms in people who have photosensitive epilepsy, vestibular disorders, or other perceptual issues. Web Accessibility: Understanding Colors and Luminance While understanding color, luminance, and saturation is important for design and readability for all sighted users, they are essential for those with reduced vision and color-deficient vision and those with specific neurological, cognitive, and other impairments. Web accessibility for seizures and physical reactions Some types of visual web content can induce seizures in people with certain brain disorders. This article helps you understand the types of content that can be problematic and find tools and strategies to help you avoid them. ARIA This is a collection of articles to learn how to use Accessible Rich Internet Applications (ARIA) to make your HTML documents more accessible. References ARIA reference Reference documentation for Accessible Rich Internet Applications (ARIA) attributes and roles. See also Developer guides WAI Interest Group Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Oct 2, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Accessibility Guides Information for web authors Personalization to help browse safely Accessible web applications and widgets Keyboard-navigable JavaScript widgets Mobile accessibility checklist Cognitive accessibility Spatial patterns Colors and Luminance Preventing seizures and physical reactions Understanding WCAG Keyboard accessible Operable Perceivable Robust Text labels and names Understandable ARIA ARIA guides ARIA live regions Screen reader implementors guide Using ARIA: Roles, states, and properties Using ARIA for labels with embedded fields ARIA reference Attributes aria-activedescendant aria-atomic aria-autocomplete aria-braillelabel aria-brailleroledescription aria-busy aria-checked aria-colcount aria-colindex aria-colindextext aria-colspan aria-controls aria-current aria-describedby aria-description aria-details aria-disabled aria-dropeffect Deprecated aria-errormessage aria-expanded aria-flowto aria-grabbed Deprecated aria-haspopup aria-hidden aria-invalid aria-keyshortcuts aria-label aria-labelledby aria-level aria-live aria-modal aria-multiline aria-multiselectable aria-orientation aria-owns aria-placeholder aria-posinset aria-pressed aria-readonly aria-relevant aria-required aria-roledescription aria-rowcount aria-rowindex aria-rowindextext aria-rowspan aria-selected aria-setsize aria-sort aria-valuemax aria-valuemin aria-valuenow aria-valuetext Roles alert alertdialog application article banner button cell checkbox columnheader combobox command comment complementary composite contentinfo definition dialog directory Deprecated document feed figure form generic grid gridcell group heading img input landmark link list listbox listitem log main mark marquee math menu menubar menuitem menuitemcheckbox menuitemradio meter navigation none note option presentation progressbar radio radiogroup range region roletype row rowgroup rowheader scrollbar search searchbox section sectionhead select separator slider spinbutton status Structural structure suggestion switch tab table tablist tabpanel term textbox timer toolbar tooltip tree treegrid treeitem widget window Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/user-preferences#what-default-preferences-control | User Preferences - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences User Preferences Tenant Preferences Preference Evaluation Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Preferences User Preferences Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Preferences User Preferences OpenAI Open in ChatGPT Learn how user preferences work in SuprSend and how to capture them. OpenAI Open in ChatGPT Before you start: Make sure you’ve set up notification categories first. See Manage Categories and Preferences for step-by-step instructions. Preferences let users control which notifications they receive. Instead of an all-or-nothing approach, users can opt out of specific categories, choose preferred channels, and set notification frequency. This granular control reduces the chance that users disable all notifications from your platform. In SuprSend, you can use ready-made UI and APIs to manage multi-tenant preference use cases. This includes letting admins set preferences for internal teams and handle notifications for enterprise customers, where companies, customers, and end users have distinct preferences. How It Works Preferences are evaluated in priority order: User Preference → Tenant Default → Category Default Three Levels of Control Global channel opt-outs, category preferences, and channel opt-outs within categories What are user preferences? Preferences only work with sub-categories: User preferences apply to sub-categories you create, not root-categories (System, Transactional, Promotional). Use sub-category slugs in workflows for preferences to work. Each user has a preference set that controls which notifications they receive. A preference set has three levels of control: channel_preferences — Global channel opt-outs (e.g., opt out of all email) categories — Category-level preferences (opt in/out of all channels of a notification type) opt_out_channels — Opt-in/out of specific channels within a category Example: Copy Ask AI { "channel_preferences" : [ { "channel" : "email" , "is_restricted" : true } ], "categories" : [ { "category" : "invoice-ready" , "preference" : "opt_out" }, { "category" : "payment-reminder" , "preference" : "opt_in" , "opt_out_channels" : [ "slack" ] } ] } In this example: user opted out of email globally, opted out of invoice-ready category completely, and stays opted in to payment-reminder but without Slack. How preferences are determined When a user hasn’t set their own preferences in a category, SuprSend uses defaults in this order: User Preference — Individual user’s explicit choices (highest priority) Tenant Default Preference — Default preferences set by tenant for the category Category Default Preference — Default preferences set at the category level (lowest priority) Preference precedence: User Preference → Tenant Default Preference → Category Default Preference Preference precedence is determined at category level . So, if a user overrides preference for a category but doesn’t touch other categories, defaults continue to apply to the untouched categories. Setting up preference categories Before users can set their preferences, you must first create and configure preference categories. For step-by-step setup instructions, see Manage Categories and Preferences . Default preferences Default preferences determine how users receive notifications when they haven’t set their own preferences. Configure these at the sub-category level when setting up categories. What default preferences control Default preferences control: Channel or Category defaults : Which categories or channels will be turned on/off by default on users’ preference page. Mandatory channels : Which channel or category users cannot opt out of (shown as disabled on preference page) Visibility : Whether a category appears on the preference page Preference types On — Users receive this category's notifications by default Users will receive notifications in this category by default. You can configure Opt-in Channels to specify which channels are included in the default “On” state: All : All available channels are enabled by default Selected Channels only : Only specific channels you select are enabled by default (e.g., Email, Android Push, iOS Push, In-App Inbox, MS Teams, Slack) Off — Users must opt in to get notifications Users will not receive notifications unless they change the preference. Can't Unsubscribe — Users cannot opt out of mandatory channels in this category Prevents users from fully opting out of the category. When selected, you can configure: Mandatory Channels : Channels which can’t be opted out of by the user. Set to “All” or “Selected Channels”. Opt-in Channels : In case of “Selected” Mandatory Channels, you can configure the channels that will be opted in by default. Channels other than mandatory and opt-in will be skipped for sending notification unless user explicitly opts in to them. Even when a category is set to “Can’t Unsubscribe,” users can still control channel-level preferences if your channel-level settings allow it. This configuration gives you fine-grained control over which channels a user is opted into by default, letting you differentiate between must-deliver channels, default-on channels, and optional channels. Capturing user preferences Users can set their preferences through one of the following methods: Hosted preference page Once you publish preference categories, SuprSend automatically generates a dedicated unsubscription webpage for collecting user preferences . Users can set channel-specific preferences from the hosted page. If the link is included in an email, the hosted page will show and save email preferences. Include it in your templates using {{$hosted_preference_url}} . This page is currently hosted on a SuprSend domain, but you can reach out to [email protected] if you’d prefer it hosted on your own domain. Embed in your product You can embed the preference interface directly inside your product using SuprSend’s ready-made UI components. SDKs exist in the languages below. Update your product preference page link on the tenant page and render it in templates using {{$embedded_preference_url}} . Javascript React Angular Embeddable preference page Controlling what categories to show on UI It’s always a good practice to show only the categories that are relevant to the user. There are two ways to achieve this: Hide categories for tenant users In a multi-tenant setup, tenants or admins can control which categories their users see. Setting visible_to_subscriber: false in tenant preferences hides the category from tenant users’ preference pages. Hidden categories won’t send notifications to those users, even if they previously opted in. Filter categories with tags Use tags to show categories based on user roles, departments, or teams. Filter categories in the preference center using the tags query parameter. 1 Setting Preference tags Tags can be added to sections and sub-categories directly from Developers → Notification Categories in the SuprSend Console. When a tag is assigned at the section level, it automatically applies to all categories under that section—so filtering by a section tag also filters its child categories. 2 Filter Categories with Tags You can filter categories using the tags query parameter in the API. This can be a simple tag match (e.g. tags=tag1 ) or a more advanced filter using logical operators. Supported operators: Operator Operand Datatype Description Example exists boolean Returns categories where any tag is set tags={ "exists": true } not string Excludes categories that have the specified tag tags={ "not": "admin" } or array Returns categories that match any of the provided tags tags={ "or": ["sales", "marketing"] } and array Returns categories that match all provided tags tags={ "and": ["sales", "manager"] } You can combine these operators for nested filtering like tags={ "or": [{ "and": ["sales", "manager"] }, { "and": ["marketing", "associate"] }] } . If no tags are provided, the preference center returns all visible categories. For details on how tags work, see Tags . Translating preference categories in user’s locale Upload translation files for your category names and descriptions. See How to manage Category translations for details. Once uploaded, pass a locale parameter (e.g., es , fr , de ) when: Loading the embeddable preference center As a query parameter in the get user preference API . The hosted preference page picks the locale from user’s profile. On hosted preference page, Dynamic content (category names, descriptions) is translated using translation files you upload. Static content (CTA text, labels, buttons, etc.) is translated automatically using SuprSend’s built-in i18n support for commonly used languages. You can see the list of supported languages below. Supported languages Language Code English en Spanish es French fr German de Italian it Portuguese pt Catalan ca Russian ru Dutch nl Polish pl Japanese ja Vietnamese vi Language Code Indonesian id Korean ko Serbian sr Norwegian no Hebrew he Chinese zh Finnish fi Swedish sv Czech cs Lithuanian lt Arabic ar How preferences are evaluated SuprSend evaluates user preferences at send time. For every recipient, the system checks user-level preferences first, then tenant-level overrides, and finally category defaults. For detailed information on the evaluation process, see Preference Evaluation . Other ways to unsubcribe from notifications In addition to the preference center within SuprSend, communication channels provide their own opt-out options, which SuprSend manages internally. Email: Unsubscribe URL header Gmail requires an unsubscribe URL in email headers when sending bulk emails (5,000+ emails/day). Most email providers expect you to add your own unsubscription page or offer a basic all-or-nothing opt-out option. You can add {{$hosted_preference_url}} here to load the SuprSend hosted preference page from the email header. Inbox (In-App): Render preference page inside your Inbox Companies also give users the option to load preference settings inside their in-app Inbox or provide a link to redirect users to the Preference center in their product. Mobile Push: Preference Page in App settings For mobile push notifications, users typically manage their preferences through the app settings. The category you assign in your workflow is also sent as the push “category” (used by Android/iOS to group notifications). If you set preference categories, the system automatically reflects them in the user’s app settings, loading similar preference controls. SMS & Whatsapp: Reply `STOP` Users generally unsubscribe from Short Message Service (SMS) by replying “STOP.” SuprSend automatically marks the SMS channel as inactive in the user’s profile when it receives a STOP reply. For WhatsApp, opt-out behavior depends on the provider; where supported, users can reply STOP and SuprSend will mark the channel inactive. FAQ How do I set up a digest schedule? You can create sub-categories for different digest schedules or set the digest schedule in the user profile and pass a dynamic schedule in the workflow digest node. An option to set the digest schedule directly on your preference page will be available soon. I have a use case where a company has multiple departments/roles, and the admin will set preferences for users in these departments. You can manage this with tenant preferences. In the SuprSend system, each tenant represents an organization, and the administrator sets which categories to send to their internal team using the tenant preference API . What happens to existing user preference view if I change default preference setting? Changing the default preference for a category doesn’t affect users who have already made changes to that category. For categories where users haven’t made any changes, the preferences update according to the new default settings. I have multiple enterprise customers with various product offerings. Customers should only receive notifications for the products they have enabled, and the same should be visible on their preference page. How can I manage this in SuprSend? You can turn off categories for tenants from the tenant page on the SuprSend console. Turning off the preference for a category automatically removes it from the tenant preference APIs and UI view. To further apply this to the tenant’s users, set visible to subscriber to false in the default tenant preferences to hide the category from the tenant’s end users. Why don't I see the 'inbox' channel in my user preferences? The inbox channel preference is behind a feature flag and needs to be enabled for your account. If you don’t see the inbox channel in your user preferences, contact [email protected] to have the feature flag enabled for your workspace. Why do users still receive promotional notifications even after unsubscribing from all categories? Unsubscribing from top-level categories (System, Transactional, Promotional) is not supported . Preferences only work with sub-categories you create. If you’re sending notifications using a top-level category like "promotional" in your workflows, users cannot unsubscribe from those notifications through the preference center, even if they unsubscribe from all visible categories. Solution: Create sub-categories under the Promotional category (e.g., “Marketing”, “Newsletter”, “Product Updates”) and use those sub-category slugs in your workflows instead of the top-level category. This allows users to: See and control preferences for each notification type Opt out of specific sub-categories Have their preferences respected when you send notifications Best practice: Organize notifications into meaningful sub-categories rather than using top-level categories directly. This provides users with granular control and improves their experience. Can I use user preferences in workflow branching to control which notifications are sent? User preferences are not passed in the workflow payload, so you cannot directly access them in branch conditions or other workflow nodes. Workaround: If you need to use preference-based logic in workflows (e.g., to route notifications based on user preferences or combine multiple notification scenarios in a single workflow), you can: Store the same preference data as custom properties in the user profile Use those custom properties in branch conditions to route notifications Example use case: If you want to combine multiple notification scenarios (e.g., “New Comment”, “Reply on my comment”, “I am mentioned”) in a single workflow to avoid duplicate notifications, you can: Store user preferences for each scenario as custom properties (e.g., wants_new_comment_notifications: true , wants_mention_notifications: true ) Use branch conditions to check these properties and route notifications accordingly This allows you to have one workflow that handles all scenarios while respecting user preferences Alternative approach: Create separate workflows for each notification scenario with conditions in the Trigger node. Each workflow can use its own preference category, allowing users to control each scenario independently. How do I let users control both notification on/off and the time they want to be reminded (e.g., medicine reminders)? You can combine preference categories with dynamic digest schedules to achieve this: 1. Set up preference categories: Create a preference category (e.g., “medicine-reminders”) that users can opt in/out of using the preference APIs or preference center UI . 2. Store time preference as user property: When users select their preferred reminder time, store it as a custom property in their user profile. For example: Copy Ask AI user.set({ "medicineReminderTime" : { "frequency" : "daily" , "time" : "09:00" , "tz_selection" : "recipient" } }) 3. Use dynamic schedule in digest node: In your workflow’s digest node, configure it to use a dynamic schedule that references the user property (e.g., ."$recipient".medicineReminderTime ). The digest will only send if the user has opted in to the category, and it will send at their preferred time. Implementation flow: Client side (React Native) : Capture user’s time preference and call your backend API Server side (Supabase Edge Function) : Update both the user’s preference (opt in/out) via SuprSend preference API and store the time preference as a user property Workflow : Use preference category to control on/off, and dynamic schedule to control timing For detailed information, see Dynamic Schedule in the digest documentation. Related documentation Notification Categories - Setting up categories & defaults Manage Categories and Preferences - Complete guide to setting up and managing categories and preferences Tenant Preferences - Managing tenant-level preferences Preference Evaluation - How SuprSend evaluates preferences at runtime Was this page helpful? Yes No Suggest edits Raise issue Previous Tenant Preferences Learn how to manage preferences for your tenants and their users. Next ⌘ I x github linkedin youtube Powered by On this page What are user preferences? How preferences are determined Setting up preference categories Default preferences What default preferences control Preference types Capturing user preferences Hosted preference page Embed in your product Controlling what categories to show on UI Hide categories for tenant users Filter categories with tags Translating preference categories in user’s locale How preferences are evaluated Other ways to unsubcribe from notifications FAQ Related documentation | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/HTTP | HTTP: Hypertext Transfer Protocol | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTTP Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) HTTP: Hypertext Transfer Protocol HTTP is an application-layer protocol for transmitting hypermedia documents, such as HTML. It was designed for communication between web browsers and web servers, but it can also be used for other purposes, such as machine-to-machine communication, programmatic access to APIs, and more. HTTP follows a classical client-server model , with a client opening a connection to make a request, then waiting until it receives a response from the server. HTTP is a stateless protocol , meaning that the server does not keep any session data between two requests, although the later addition of cookies adds state to some client-server interactions. In this article Guides Tools & resources Reference Guides HTTP is an extensible protocol that relies on concepts like resources and Uniform Resource Identifiers (URIs), a basic message structure, and client-server communication model. On top of these concepts, numerous extensions have been developed over the years that add functionality and updated semantics, including additional HTTP methods and headers. The HTTP guides are listed in order from general overviews to specialized, use-case-driven topics. Beginners are encouraged to start with the foundational guides before exploring more focused articles. Overview of HTTP The basic features of HTTP, what it can do, its intended use in web architecture, and its position in the protocol stack. Evolution of HTTP HTTP was created in the early 1990s and has been extended several times. This article goes through its history and describes HTTP/0.9, HTTP/1.0, HTTP/1.1, through HTTP/2 and HTTP/3, as well as novelties introduced over the years. A typical HTTP session Describes the flow of an HTTP session, from establishing a connection, sending a request, to receiving a response. HTTP messages HTTP messages transmitted as requests and responses have a defined structure. This article describes this general structure, its purpose, and the different types of messages. MIME types Since HTTP/1.0, different types of content can be transmitted. This article explains how this is accomplished using the Content-Type header and the MIME standard. A shortlist of common types used by web developers can be found in Common MIME types . Compression in HTTP Browsers and servers compress their messages before sending them over the network to reduce the amount of data that needs to be transmitted, improving transfer speed and bandwidth utilization. HTTP caching Caching is a highly important mechanism for delivering fast experiences on the Web and for efficient use of resources. This article describes different methods of caching and how to use HTTP headers to control them. HTTP authentication Authentication is a way to verify the identity of a client when making requests to a server. It ensures that only authorized users or systems can access certain resources. Using HTTP cookies Although HTTP is a stateless protocol, a server can send a Set-Cookie header with the response. The client then returns the cookie's value with every subsequent request to the server in the form of a Cookie request header. This adds the ability to store and exchange a small amount of data which effectively adds state to some client-server interactions. Redirections in HTTP URL redirection, also known as URL forwarding, is a technique to give more than one URL address to a page, a form, a whole website, or a web application. HTTP has a special kind of response, called a HTTP redirect, for this operation. HTTP conditional requests In conditional requests, the outcome of a request depends on the value of a validator in the request. This method is used heavily in caching and use cases such as resuming a download, preventing lost updates when modifying a document on the server, and more. HTTP range requests A range request asks the server to send a specific part (or parts) of a resource back to a client instead of the full resource. Range requests are useful for cases when a client knows they need only part of a large file, or for cases where an application allows the user to pause and resume a download. Content negotiation HTTP defines a set of message headers, starting with Accept as a way for a browser to announce the format, language, or encoding it prefers. This article explains how this advertisement happens, how the server is expected to react, and how it chooses the most adequate response to a request. Connection management in HTTP/1.x HTTP/1.1 was the first version of HTTP to support persistent connections and pipelining. This article explains both concepts, including the pros and cons of each. Protocol upgrade mechanism HTTP/1.1 provides a mechanism to upgrade an already-established connection to a different protocol using the Upgrade header. A client can upgrade a connection from HTTP/1.1 to HTTP/2, or an HTTP(S) connection to a WebSocket ( ws / wss ). Proxy servers and tunneling A proxy can be on the user's local computer, or anywhere between the user's computer and a destination server on the Internet. This page outlines some basics about proxies and introduces a few configuration options. HTTP Client hints Client Hints are a set of response headers that a server can use to proactively request information from a client about the device, network, user, and user-agent-specific preferences. The server can then determine which resources to send, based on the information that the client chooses to provide. Network Error Logging Experimental Network Error Logging is a mechanism that can be configured via the NEL HTTP response header. This experimental header allows websites and applications to opt-in to receive reports about failed (or even successful) network fetches from supporting browsers. Browser detection using the user agent It's very rarely a good idea to use user agent sniffing to detect a browser, but there are edge cases that require it. This document will guide you in doing this as correctly as possible when this is necessary, with an emphasis on considerations to make before embarking on this route. Security and privacy Permissions Policy Permissions Policy provides mechanisms for web developers to explicitly declare what functionality can and cannot be used on a website. You define a set of "policies" that restrict what APIs the site's code can access or modify the browser's default behavior for certain features. Cross-Origin Resource Sharing (CORS) Cross-site HTTP requests are requests for resources from a different domain than that of the resource making the request. Web pages today very commonly load cross-site resources, for example, a page 'Domain A' ( http://domaina.example/ ) requests an image on 'Domain B' ( http://domainb.foo/image.jpg ) via the img element. CORS allows web developers to control how their site reacts to cross-site requests. Content Security Policy (CSP) CSP allows website administrators to use the Content-Security-Policy response header to control which resources the client is allowed to load for a given page. The CSP guide describes the overall Content Security Policy mechanism which helps detect and mitigate certain types of attacks, including Cross-Site Scripting (XSS) and data injection attacks. Cross-Origin Resource Policy (CORP) CORP lets websites and applications opt in to protection against specific requests from other origins (such as those issued with elements like <script> and <img> ), to mitigate speculative side-channel attacks. Mozilla web security guidelines A collection of tips to help operational teams with creating secure web applications. Related resources URIs Uniform Resource Identifiers (URIs) are used to describe and locate resources on the web and are an essential component in HTTP requests. Configuring servers for Ogg media This guide covers a few server configuration changes that may be necessary for your web server to correctly serve Ogg media files. This information may also be useful if you encounter other media types your server isn't already configured to recognize. Tools & resources Helpful tools and resources for understanding and debugging HTTP. Firefox Developer Tools Network monitor HTTP Observatory A project designed to help developers, system administrators, and security professionals configure their sites safely and securely. RedBot Tools to check your cache-related headers. nghttp2 An HTTP/2 client, server and proxy implementation written in C with load test and benchmarking tools and an HPACK encoder and decoder. curl A command-line tool for transferring data specified with URL syntax. Supports HTTP, HTTPS, WS, WSS, among many other protocols. How Browsers Work (2011) A very comprehensive article on browser internals and request flow through HTTP protocol. Reference The HTTP reference documentation contains detailed information about headers, request methods, status responses, and lists relevant specifications and standards documents. HTTP headers Message headers are used to send metadata about a resource or a HTTP message, and to describe the behavior of the client or the server. HTTP request methods Request methods indicate the purpose of the request and what is expected if the request is successful. The most common methods are GET and POST for retrieving and sending data to servers, respectively, but there are other methods which serve different purposes. HTTP response status codes Response status codes indicate the outcome of a specific HTTP request. Responses are grouped in five classes: informational, successful, redirections, client errors, and server errors. HTTP resources and specifications This page lists relevant resources about HTTP since it was first specified in the early 1990s. The following subsections are also notable: CSP directives The Content-Security-Policy (CSP) response header allows website administrators to specify which resources the user agent is allowed to load for a given page. This section lists directives that can be used in a CSP header, with individual documentation pages that describe how the directives work and how to use them. Permissions-Policy directives The Permissions-Policy response header provides a mechanism to allow or deny the use of browser features in a document or within any <iframe> element in the document. This section lists directives that can be used in a Permissions-Policy header, with individual documentation pages that describe how the directives work and how to use them. Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 22, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTTP Guides Overview of HTTP Evolution of HTTP A typical HTTP session HTTP messages Media types Common types Compression in HTTP HTTP caching HTTP authentication Using HTTP cookies Redirections in HTTP Conditional requests Range requests Client hints User-Agent reduction Compression Dictionary Transport Experimental Network Error Logging Experimental Content negotiation Default Accept values Browser detection using the UA string Connection management in HTTP/1.x Protocol upgrade mechanism Proxy servers and tunneling Proxy Auto-Configuration (PAC) file Security and privacy HTTP Observatory Practical implementation guides Permissions Policy Experimental Cross-Origin Resource Policy (CORP) IFrame credentialless Experimental Cross-Origin Resource Sharing (CORS) CORS errors Reason: CORS disabled Reason: CORS header 'Access-Control-Allow-Origin' does not match 'xyz' Reason: CORS header 'Access-Control-Allow-Origin' missing Reason: CORS header 'Origin' cannot be added Reason: CORS preflight channel did not succeed Reason: CORS request did not succeed Reason: CORS request external redirect not allowed Reason: CORS request not HTTP Reason: Credential is not supported if the CORS header 'Access-Control-Allow-Origin' is '*' Reason: Did not find method in CORS header 'Access-Control-Allow-Methods' Reason: expected 'true' in CORS header 'Access-Control-Allow-Credentials' Reason: invalid token 'xyz' in CORS header 'Access-Control-Allow-Headers' Reason: invalid token 'xyz' in CORS header 'Access-Control-Allow-Methods' Reason: missing token 'xyz' in CORS header 'Access-Control-Allow-Headers' from CORS preflight channel Reason: Multiple CORS header 'Access-Control-Allow-Origin' not allowed Content Security Policy (CSP) Errors and warnings Reference HTTP headers Accept Accept-CH Accept-Encoding Accept-Language Accept-Patch Accept-Post Accept-Ranges Access-Control-Allow-Credentials Access-Control-Allow-Headers Access-Control-Allow-Methods Access-Control-Allow-Origin Access-Control-Expose-Headers Access-Control-Max-Age Access-Control-Request-Headers Access-Control-Request-Method Activate-Storage-Access Age Allow Alt-Svc Alt-Used Attribution-Reporting-Eligible Deprecated Attribution-Reporting-Register-Source Deprecated Attribution-Reporting-Register-Trigger Deprecated Authorization Available-Dictionary Experimental Cache-Control Clear-Site-Data Connection Content-Digest Content-Disposition Content-DPR Non-standard Deprecated Content-Encoding Content-Language Content-Length Content-Location Content-Range Content-Security-Policy Content-Security-Policy-Report-Only Content-Type Cookie Critical-CH Experimental Cross-Origin-Embedder-Policy Cross-Origin-Opener-Policy Cross-Origin-Resource-Policy Date Device-Memory Non-standard Deprecated Dictionary-ID Experimental DNT Non-standard Deprecated Downlink Experimental DPR Non-standard Deprecated Early-Data Experimental ECT Experimental ETag Expect Expect-CT Deprecated Expires Forwarded From Host Idempotency-Key Experimental If-Match If-Modified-Since If-None-Match If-Range If-Unmodified-Since Integrity-Policy Integrity-Policy-Report-Only Keep-Alive Last-Modified Link Location Max-Forwards NEL Experimental No-Vary-Search Experimental Observe-Browsing-Topics Non-standard Deprecated Origin Origin-Agent-Cluster Permissions-Policy Experimental Pragma Deprecated Prefer Preference-Applied Priority Proxy-Authenticate Proxy-Authorization Range Referer Referrer-Policy Refresh Report-To Non-standard Deprecated Reporting-Endpoints Repr-Digest Retry-After RTT Experimental Save-Data Experimental Sec-Browsing-Topics Non-standard Deprecated Sec-CH-Device-Memory Experimental Sec-CH-DPR Experimental Sec-CH-Prefers-Color-Scheme Experimental Sec-CH-Prefers-Reduced-Motion Experimental Sec-CH-Prefers-Reduced-Transparency Experimental Sec-CH-UA Experimental Sec-CH-UA-Arch Experimental Sec-CH-UA-Bitness Experimental Sec-CH-UA-Form-Factors Experimental Sec-CH-UA-Full-Version Deprecated Sec-CH-UA-Full-Version-List Experimental Sec-CH-UA-Mobile Experimental Sec-CH-UA-Model Experimental Sec-CH-UA-Platform Experimental Sec-CH-UA-Platform-Version Experimental Sec-CH-UA-WoW64 Experimental Sec-CH-Viewport-Height Experimental Sec-CH-Viewport-Width Experimental Sec-CH-Width Experimental Sec-Fetch-Dest Sec-Fetch-Mode Sec-Fetch-Site Sec-Fetch-Storage-Access Sec-Fetch-User Sec-GPC Experimental Sec-Private-State-Token Experimental Sec-Private-State-Token-Crypto-Version Experimental Sec-Private-State-Token-Lifetime Experimental Sec-Purpose Sec-Redemption-Record Experimental Sec-Speculation-Tags Experimental Sec-WebSocket-Accept Sec-WebSocket-Extensions Sec-WebSocket-Key Sec-WebSocket-Protocol Sec-WebSocket-Version Server Server-Timing Service-Worker Service-Worker-Allowed Service-Worker-Navigation-Preload Set-Cookie Set-Login SourceMap Speculation-Rules Experimental Strict-Transport-Security Supports-Loading-Mode Experimental TE Timing-Allow-Origin Tk Non-standard Deprecated Trailer Transfer-Encoding Upgrade Upgrade-Insecure-Requests Use-As-Dictionary Experimental User-Agent Vary Via Viewport-Width Non-standard Deprecated Want-Content-Digest Want-Repr-Digest Warning Deprecated Width Non-standard Deprecated WWW-Authenticate X-Content-Type-Options X-DNS-Prefetch-Control Non-standard X-Forwarded-For Non-standard X-Forwarded-Host Non-standard X-Forwarded-Proto Non-standard X-Frame-Options X-Permitted-Cross-Domain-Policies Non-standard X-Powered-By Non-standard X-Robots-Tag Non-standard X-XSS-Protection Non-standard Deprecated HTTP request methods CONNECT DELETE GET HEAD OPTIONS PATCH POST PUT TRACE HTTP response status codes 100 Continue 101 Switching Protocols 102 Processing 103 Early Hints 200 OK 201 Created 202 Accepted 203 Non-Authoritative Information 204 No Content 205 Reset Content 206 Partial Content 207 Multi-Status 208 Already Reported 226 IM Used 300 Multiple Choices 301 Moved Permanently 302 Found 303 See Other 304 Not Modified 307 Temporary Redirect 308 Permanent Redirect 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 409 Conflict 410 Gone 411 Length Required 412 Precondition Failed 413 Content Too Large 414 URI Too Long 415 Unsupported Media Type 416 Range Not Satisfiable 417 Expectation Failed 418 I'm a teapot 421 Misdirected Request 422 Unprocessable Content 423 Locked 424 Failed Dependency 425 Too Early 426 Upgrade Required 428 Precondition Required 429 Too Many Requests 431 Request Header Fields Too Large 451 Unavailable For Legal Reasons 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 505 HTTP Version Not Supported 506 Variant Also Negotiates 507 Insufficient Storage 508 Loop Detected 510 Not Extended 511 Network Authentication Required CSP directives base-uri block-all-mixed-content Deprecated child-src connect-src default-src fenced-frame-src Experimental font-src form-action frame-ancestors frame-src img-src manifest-src media-src object-src prefetch-src Non-standard Deprecated report-to report-uri Deprecated require-trusted-types-for sandbox script-src script-src-attr script-src-elem style-src style-src-attr style-src-elem trusted-types upgrade-insecure-requests worker-src Permissions-Policy directives Experimental accelerometer Experimental ambient-light-sensor Experimental aria-notify Experimental Non-standard attribution-reporting Deprecated autoplay Experimental bluetooth Experimental browsing-topics Non-standard Deprecated camera Experimental captured-surface-control Experimental compute-pressure Experimental cross-origin-isolated Experimental deferred-fetch Experimental deferred-fetch-minimal Experimental display-capture Experimental encrypted-media Experimental fullscreen Experimental gamepad Experimental geolocation Experimental gyroscope Experimental hid Experimental identity-credentials-get Experimental idle-detection Experimental language-detector Experimental local-fonts Experimental magnetometer Experimental microphone Experimental midi Experimental on-device-speech-recognition Experimental otp-credentials Experimental payment Experimental picture-in-picture Experimental private-state-token-issuance Experimental private-state-token-redemption Experimental publickey-credentials-create Experimental publickey-credentials-get Experimental screen-wake-lock Experimental serial Experimental speaker-selection Experimental storage-access Experimental summarizer Experimental translator Experimental usb Experimental web-share Experimental window-management Experimental xr-spatial-tracking Experimental HTTP resources and specifications Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://www.youtube.com/playlist?list=PLcx_iGeB-Nxi54fIfinPnGfn6lPOLnLXQ | API Specifications Conference (ASC) 2021, September 28-29 - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/HTML/Guides/Cheatsheet | HTML cheatsheet for syntax and common tasks - HTML | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTML Guides Cheatsheet Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 中文 (简体) HTML cheatsheet for syntax and common tasks While using HTML it can be very handy to have an easy way to remember how to use HTML tags properly and how to apply them. MDN provides you with extended HTML reference documentation as well as a deep instructional set of HTML guides . However, in many cases we just need some quick hints as we go. That's the whole purpose of the cheat sheet, to give you some quick accurate ready to use code snippets for common usages. Note: HTML tags must be used for their semantic value, not their appearance. It's always possible to totally change the look and feel of a given tag using CSS so, when using HTML, take the time to focus on the meaning rather than the appearance. In this article Inline elements Block elements Inline elements An "element" is a single part of a webpage. Some elements are large and hold smaller elements like containers. Some elements are small and are "nested" inside larger ones. By default, "inline elements" appear next to one another in a webpage. They take up only as much width as they need in a page and fit together horizontally like words in a sentence or books shelved side-by-side in a row. All inline elements can be placed within the <body> element. Inline elements: usage and examples Usage Element Example A link <a> html <a href="https://example.org"> A link to example.org</a>. An image <img> html <img src="beast.png" width="50" /> An inline container <span> html Used to group elements: for example, to <span style="color:blue">style them</span>. Emphasize text <em> html <em>I'm posh</em>. Italic text <i> html Mark a phrase in <i>italics</i>. Bold text <b> html Bold <b>a word or phrase</b>. Important text <strong> html <strong>I'm important!</strong> Highlight text <mark> html <mark>Notice me!</mark> Strikethrough text <s> html <s>I'm irrelevant.</s> Subscript <sub> html H<sub>2</sub>O Small text <small> html Used to represent the <small>small print </small>of a document. Address <address> html <address>Main street 67</address> Textual citation <cite> html For more monsters, see <cite>The Monster Book of Monsters</cite>. Superscript <sup> html x<sup>2</sup> Inline quotation <q> html <q>Me?</q>, she said. A line break <br> html Line 1<br />Line 2 A possible line break <wbr> html <div style="width: 200px"> Llanfair<wbr />pwllgwyngyll<wbr />gogerychwyrndrobwllllantysiliogogogoch. </div> Date <time> html Used to format the date. For example: <time datetime="2020-05-24"> published on 23-05-2020</time>. Code format <code> html This text is in normal format, but <code>this text is in code format</code>. Audio <audio> html <audio controls> <source src="/shared-assets/audio/t-rex-roar.mp3" type="audio/mpeg" /> </audio> Video <video> html <video controls width="250" src="/shared-assets/videos/flower.webm" > <a href="/shared-assets/videos/flower.webm">Download WebM video</a> </video> Block elements "Block elements," on the other hand, take up the entire width of a webpage. They also take up a full line of a webpage; they do not fit together side-by-side. Instead, they stack like paragraphs in an essay or toy blocks in a tower. Note: Because this cheat sheet is limited to a few elements representing specific structures or having special semantics, the div element is intentionally not included — because the div element doesn't represent anything and doesn't have any special semantics. Usage Element Example A simple paragraph <p> html <p>I'm a paragraph</p> <p>I'm another paragraph</p> An extended quotation <blockquote> html They said: <blockquote>The blockquote element indicates an extended quotation.</blockquote> Additional information <details> html <details> <summary>HTML Cheat Sheet</summary> <p>Inline elements</p> <p>Block elements</p> </details> An unordered list <ul> html <ul> <li>I'm an item</li> <li>I'm another item</li> </ul> An ordered list <ol> html <ol> <li>I'm the first item</li> <li>I'm the second item</li> </ol> A definition list <dl> html <dl> <dt>A Term</dt> <dd>Definition of a term</dd> <dt>Another Term</dt> <dd>Definition of another term</dd> </dl> A horizontal rule <hr> html before<hr />after Text Heading <h1>-<h6> html <h1> This is Heading 1 </h1> <h2> This is Heading 2 </h2> <h3> This is Heading 3 </h3> <h4> This is Heading 4 </h4> <h5> This is Heading 5 </h5> <h6> This is Heading 6 </h6> Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 3, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTML Guides Cheatsheet Comments Constraint validation Content categories Date and time formats Microdata Microformats Quirks and standards modes Responsive images How to Define terms with HTML Use data attributes Use cross-origin images Add a hitmap on top of an image Author fast-loading HTML pages Add JavaScript Reference Elements <a> <abbr> <acronym> Deprecated <address> <area> <article> <aside> <audio> <b> <base> <bdi> <bdo> <big> Deprecated <blockquote> <body> <br> <button> <canvas> <caption> <center> Deprecated <cite> <code> <col> <colgroup> <data> <datalist> <dd> <del> <details> <dfn> <dialog> <dir> Deprecated <div> <dl> <dt> <em> <embed> <fencedframe> Experimental <fieldset> <figcaption> <figure> <font> Deprecated <footer> <form> <frame> Deprecated <frameset> Deprecated <h1> <head> <header> <hgroup> <hr> <html> <i> <iframe> <img> <input> <ins> <kbd> <label> <legend> <li> <link> <main> <map> <mark> <marquee> Deprecated <menu> <meta> <meter> <nav> <nobr> Deprecated <noembed> Deprecated <noframes> Deprecated <noscript> <object> <ol> <optgroup> <option> <output> <p> <param> Deprecated <picture> <plaintext> Deprecated <pre> <progress> <q> <rb> Deprecated <rp> <rt> <rtc> Deprecated <ruby> <s> <samp> <script> <search> <section> <select> <selectedcontent> Experimental <slot> <small> <source> <span> <strike> Deprecated <strong> <style> <sub> <summary> <sup> <table> <tbody> <td> <template> <textarea> <tfoot> <th> <thead> <time> <title> <tr> <track> <tt> Deprecated <u> <ul> <var> <video> <wbr> <xmp> Deprecated Attributes accept autocomplete capture content crossorigin dirname disabled elementtiming fetchpriority for form max maxlength min minlength multiple pattern placeholder readonly rel required size step Global attributes accesskey anchor Experimental Non-standard autocapitalize autocorrect autofocus class contenteditable data-* dir draggable enterkeyhint exportparts hidden id inert inputmode is itemid itemprop itemref itemscope itemtype lang nonce part popover slot spellcheck style tabindex title translate virtualkeyboardpolicy Experimental writingsuggestions Attributes by element <input> type <input type="button"> <input type="checkbox"> <input type="color"> <input type="date"> <input type="datetime-local"> <input type="email"> <input type="file"> <input type="hidden"> <input type="image"> <input type="month"> <input type="number"> <input type="password"> <input type="radio"> <input type="range"> <input type="reset"> <input type="search"> <input type="submit"> <input type="tel"> <input type="text"> <input type="time"> <input type="url"> <input type="week"> <script> type importmap speculationrules Experimental <meta> name color-scheme referrer robots theme-color viewport <meta> http-equiv Attribute values rel keywords rel="alternate stylesheet" rel="compression-dictionary" Experimental rel="dns-prefetch" rel="manifest" rel="me" rel="modulepreload" rel="noopener" rel="noreferrer" rel="preconnect" rel="prefetch" rel="preload" rel="prerender" Non-standard Deprecated Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps | Progressive web apps | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Progressive web apps Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Progressive web apps A progressive web app (PWA) is an app that's built using web platform technologies, but that provides a user experience like that of a platform-specific app. Like a website, a PWA can run on multiple platforms and devices from a single codebase. Like a platform-specific app, it can be installed on the device, can operate while offline and in the background, and can integrate with the device and with other installed apps. In this article Guides How to Tutorials Reference See also Guides The PWA guides provide conceptual explanations of different aspects of PWAs. They're intended to help you understand what kinds of things are possible with PWAs, and to provide enough pointers to help you understand how to achieve them. What is a progressive web app? An introduction to PWAs, comparing them with traditional websites and with platform-specific apps, and outlining their main features. Making PWAs installable One of the defining aspects of a PWA is that it can be installed on the device, and then appears to users as a platform-specific app, a permanent feature of their device which they can launch directly from the operating system like any other app. In this guide we'll explore what "installable" means, what a PWA needs to provide for it to be installable, and how you can customize the install experience. Installing and uninstalling web apps This guide covers how users can install and uninstall PWAs on their devices. Offline and background operation In this guide, we'll introduce a set of technologies that enable a PWA to provide a good user experience even when the device has intermittent network connectivity and to perform operations in the background, even when the main app is not running. Caching An overview of the APIs that enable a PWA to cache resources locally, and some common strategies used by PWAs to implement offline functionality. Best practices for PWAs PWAs should adapt to different browsers and devices, be accessible, have good performance, and integrate well with the operating system. This guide provides a list of best practices to help you make sure your PWA is as good as it can be. How to The PWA how-tos provide detailed instructions on implementing specific PWA features. Create a standalone app Describes how to specify that a PWA should be launched in its own dedicated window when it is launched, rather than a browser tab. Define your app icons Describes how to define your own set of icons to be used when the PWA is installed on a device. Customize your app's colors Describes how to set background and theme colors for a PWA. Display badges Describes how to display a badge on the PWA's icon: for example to let the user know that they have received new messages. Expose common app actions as shortcuts Describes how to expose common actions for a PWA that can be launched from the operating system's app shortcut menu. Share data between apps Describes how PWAs can share data with each other by using the operating system's app sharing mechanism. Trigger installation from your PWA Describes how developers can provide their own UI to invite users to install their PWA. Associate files with your PWA Describes how you can create an association between file types and your PWA, so that when the user clicks on the file, your PWA is launched to handle it. Tutorials Build a PWA from scratch using these PWA Tutorials , which walk through the steps from start to finish, explaining how the different features of the app are implemented along the way. Creating your first PWA This novice-level tutorial walks through the creation of a PWA to track menstrual cycles. Lessons include a walk through of the HTML, CSS, and JavaScript required to create a fully functional web app, setting up a testing environment, and complete explanations guiding the learner through upgrading the web app into a PWA; including developing and inspecting a manifest, adding a service worker, and using the service worker to delete stale caches. Deep dive into PWA This intermediate-level tutorial walks through the creation of a PWA that lists information about games submitted to the A-Frame category in the js13kGames 2017 competition. This tutorial includes all the basics for creating a PWA, with additional features, including notifications, push, and app performance. Reference Our PWA reference lists all features documented on MDN that you'll need to build a PWA. Web app manifest Web app manifest members Developers can use web app manifest members to describe a PWA, customize its appearance, and more deeply integrate it into the operating system. Service Worker APIs Communication with the app The following APIs can be used by a service worker to communicate with its associated client PWA: Client.postMessage() Allows a service worker to send a message to its client PWA. Broadcast Channel API Allows a service worker and its client PWA to establish a basic two-way communication channel. Offline operation The following APIs can be used by a service worker to make your app work offline: Cache A persistent storage mechanism for HTTP responses used to store assets that can be reused when the app is offline. Clients An interface used to provide access to the documents that are controlled by the service worker. FetchEvent An event, dispatched in the service worker with every HTTP request made by the client PWA. The event can be used to either send the request to the server as normal and save the response for future use, or intercept the request and immediately respond with a response cached previously. Background operation The following APIs can be used by a service worker to perform tasks in the background, even when your app is not running: Background Synchronization API A way to defer tasks to run in a service worker once there is a stable network connection. Web Periodic Background Synchronization API A way to register tasks to be run in a service worker at periodic intervals with network connectivity. Background Fetch API A method for a service worker to manage downloads that may take a significant amount of time, such as video or audio files. Other web APIs IndexedDB A client-side storage API for significant amounts of structured data, including files. Badging API A method of setting a badge on the application icon, providing a low-distraction notification. Notifications API A way to send notifications that are displayed at the operating system level. Web Share API A mechanism for sharing text, links, files, and other content to other apps selected by the user on their device. Window Controls Overlay API An API for PWAs installed on desktop operating systems that enables hiding the default window title bar, enabling displaying the app over the full surface area of the app window. See also Progressive web apps on web.dev Learn PWA on web.dev Progressive web apps on learn.microsoft.com (2023) Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Aug 25, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Progressive web apps Guides What is a progressive web app? Installing and uninstalling web apps Making PWAs installable Offline and background operation Caching Best practices for PWAs Tutorials CycleTracker Base HTML and CSS Secure connection JavaScript functionality Manifest and iconography Offline support using service workers js13kGames PWA structure Offline support using service workers Making PWAs installable Using Notifications and Push APIs Progressive loading How to Trigger installation from your PWA Define your app icons Create a standalone app Customize colors of your app Display a badge on the app icon Expose common app actions as shortcuts Share data between apps Associate files with your PWA Reference Web app manifest Manifest members background_color categories description display display_override Experimental file_handlers Experimental icons id launch_handler Experimental name note_taking Experimental orientation prefer_related_applications Experimental protocol_handlers Experimental related_applications Experimental scope scope_extensions Experimental screenshots serviceworker Experimental Non-standard share_target Experimental short_name shortcuts start_url theme_color Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Loops_and_iteration | Loops and iteration - JavaScript | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web JavaScript Guide Loops and iteration Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Loops and iteration Previous Next Loops offer a quick and easy way to do something repeatedly. This chapter of the JavaScript Guide introduces the different iteration statements available to JavaScript. You can think of a loop as a computerized version of the game where you tell someone to take X steps in one direction, then Y steps in another. For example, the idea "Go five steps to the east" could be expressed this way as a loop: js for (let step = 0; step < 5; step++) { // Runs 5 times, with values of step 0 through 4. console.log("Walking east one step"); } There are many different kinds of loops, but they all essentially do the same thing: they repeat an action some number of times. (Note that it's possible that number could be zero!) The various loop mechanisms offer different ways to determine the start and end points of the loop. There are various situations that are more easily served by one type of loop over the others. The statements for loops provided in JavaScript are: for statement do...while statement while statement labeled statement break statement continue statement for...in statement for...of statement In this article for statement do...while statement while statement labeled statement break statement continue statement for...in statement for...of statement for statement A for loop repeats until a specified condition evaluates to false. The JavaScript for loop is similar to the Java and C for loop. A for statement looks as follows: js for (initialization; condition; afterthought) statement When a for loop executes, the following occurs: The initializing expression initialization , if any, is executed. This expression usually initializes one or more loop counters, but the syntax allows an expression of any degree of complexity. This expression can also declare variables. The condition expression is evaluated. If the value of condition is true, the loop statements execute. Otherwise, the for loop terminates. (If the condition expression is omitted entirely, the condition is assumed to be true.) The statement executes. To execute multiple statements, use a block statement ( { } ) to group those statements. If present, the update expression afterthought is executed. Control returns to Step 2. Example In the example below, the function contains a for statement that counts the number of selected options in a scrolling list (a <select> element that allows multiple selections). HTML html <form name="selectForm"> <label for="musicTypes" >Choose some music types, then click the button below:</label > <select id="musicTypes" name="musicTypes" multiple> <option selected>R&amp;B</option> <option>Jazz</option> <option>Blues</option> <option>New Age</option> <option>Classical</option> <option>Opera</option> </select> <button id="btn" type="button">How many are selected?</button> </form> JavaScript Here, the for statement declares the variable i and initializes it to 0 . It checks that i is less than the number of options in the <select> element, performs the succeeding if statement, and increments i by 1 after each pass through the loop. js function countSelected(selectObject) { let numberSelected = 0; for (let i = 0; i < selectObject.options.length; i++) { if (selectObject.options[i].selected) { numberSelected++; } } return numberSelected; } const btn = document.getElementById("btn"); btn.addEventListener("click", () => { const musicTypes = document.selectForm.musicTypes; console.log(`You have selected ${countSelected(musicTypes)} option(s).`); }); do...while statement The do...while statement repeats until a specified condition evaluates to false. A do...while statement looks as follows: js do statement while (condition); statement is always executed once before the condition is checked. (To execute multiple statements, use a block statement ( { } ) to group those statements.) If condition is true , the statement executes again. At the end of every execution, the condition is checked. When the condition is false , execution stops, and control passes to the statement following do...while . Example In the following example, the do loop iterates at least once and reiterates until i is no longer less than 5 . js let i = 0; do { i += 1; console.log(i); } while (i < 5); while statement A while statement executes its statements as long as a specified condition evaluates to true . A while statement looks as follows: js while (condition) statement If the condition becomes false , statement within the loop stops executing and control passes to the statement following the loop. The condition test occurs before statement in the loop is executed. If the condition returns true , statement is executed and the condition is tested again. If the condition returns false , execution stops, and control is passed to the statement following while . To execute multiple statements, use a block statement ( { } ) to group those statements. Example 1 The following while loop iterates as long as n is less than 3 : js let n = 0; let x = 0; while (n < 3) { n++; x += n; } With each iteration, the loop increments n and adds that value to x . Therefore, x and n take on the following values: After the first pass: n = 1 and x = 1 After the second pass: n = 2 and x = 3 After the third pass: n = 3 and x = 6 After completing the third pass, the condition n < 3 is no longer true , so the loop terminates. Example 2 Avoid infinite loops. Make sure the condition in a loop eventually becomes false —otherwise, the loop will never terminate! The statements in the following while loop execute forever because the condition never becomes false : js // Infinite loops are bad! while (true) { console.log("Hello, world!"); } labeled statement A label provides a statement with an identifier that lets you refer to it elsewhere in your program. For example, you can use a label to identify a loop, and then use the break or continue statements to indicate whether a program should interrupt the loop or continue its execution. The syntax of the labeled statement looks like the following: js label: statement The value of label may be any JavaScript identifier that is not a reserved word. The statement that you identify with a label may be any statement. For examples of using labeled statements, see the examples of break and continue below. break statement Use the break statement to terminate a loop, switch , or in conjunction with a labeled statement. When you use break without a label, it terminates the innermost enclosing while , do-while , for , or switch immediately and transfers control to the following statement. When you use break with a label, it terminates the specified labeled statement. The syntax of the break statement looks like this: js break; break label; The first form of the syntax terminates the innermost enclosing loop or switch . The second form of the syntax terminates the specified enclosing labeled statement. Example 1 The following example iterates through the elements in an array until it finds the index of an element whose value is theValue : js for (let i = 0; i < a.length; i++) { if (a[i] === theValue) { break; } } Example 2: Breaking to a label js let x = 0; let z = 0; labelCancelLoops: while (true) { console.log("Outer loops:", x); x += 1; z = 1; while (true) { console.log("Inner loops:", z); z += 1; if (z === 10 && x === 10) { break labelCancelLoops; } else if (z === 10) { break; } } } continue statement The continue statement can be used to restart a while , do-while , for , or label statement. When you use continue without a label, it terminates the current iteration of the innermost enclosing while , do-while , or for statement and continues execution of the loop with the next iteration. In contrast to the break statement, continue does not terminate the execution of the loop entirely. In a while loop, it jumps back to the condition. In a for loop, it jumps to the increment-expression . When you use continue with a label, it applies to the looping statement identified with that label. The syntax of the continue statement looks like the following: js continue; continue label; Example 1 The following example shows a while loop with a continue statement that executes when the value of i is 3 . Thus, n takes on the values 1 , 3 , 7 , and 12 . js let i = 0; let n = 0; while (i < 5) { i++; if (i === 3) { continue; } n += i; console.log(n); } // Logs: // 1 3 7 12 If you comment out the continue; , the loop would run till the end and you would see 1,3,6,10,15 . Example 2 A statement labeled checkIandJ contains a statement labeled checkJ . If continue is encountered, the program terminates the current iteration of checkJ and begins the next iteration. Each time continue is encountered, checkJ reiterates until its condition returns false . When false is returned, the remainder of the checkIandJ statement is completed, and checkIandJ reiterates until its condition returns false . When false is returned, the program continues at the statement following checkIandJ . If continue had a label of checkIandJ , the program would continue at the top of the checkIandJ statement. js let i = 0; let j = 10; checkIandJ: while (i < 4) { console.log(i); i += 1; checkJ: while (j > 4) { console.log(j); j -= 1; if (j % 2 === 0) { continue; } console.log(j, "is odd."); } console.log("i =", i); console.log("j =", j); } for...in statement The for...in statement iterates a specified variable over all the enumerable properties of an object. For each distinct property, JavaScript executes the specified statements. A for...in statement looks as follows: js for (variable in object) statement Example The following function takes as its argument an object and the object's name. It then iterates over all the object's properties and returns a string that lists the property names and their values. js function dumpProps(obj, objName) { let result = ""; for (const i in obj) { result += `${objName}.${i} = ${obj[i]}<br>`; } result += "<hr>"; return result; } For an object car with properties make and model , result would be: car.make = Ford car.model = Mustang Arrays Although it may be tempting to use this as a way to iterate over Array elements, the for...in statement will return the name of your user-defined properties in addition to the numeric indexes. Therefore, it is better to use a traditional for loop with a numeric index when iterating over arrays, because the for...in statement iterates over user-defined properties in addition to the array elements, if you modify the Array object (such as adding custom properties or methods). for...of statement The for...of statement creates a loop Iterating over iterable objects (including Array , Map , Set , arguments object and so on), invoking a custom iteration hook with statements to be executed for the value of each distinct property. js for (variable of iterable) statement The following example shows the difference between a for...of loop and a for...in loop. While for...in iterates over property names, for...of iterates over property values: js const arr = [3, 5, 7]; arr.foo = "hello"; for (const i in arr) { console.log(i); } // "0" "1" "2" "foo" for (const i of arr) { console.log(i); } // Logs: 3 5 7 The for...of and for...in statements can also be used with destructuring . For example, you can simultaneously loop over the keys and values of an object using Object.entries() . js const obj = { foo: 1, bar: 2 }; for (const [key, val] of Object.entries(obj)) { console.log(key, val); } // "foo" 1 // "bar" 2 Previous Next Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 3, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar JavaScript Tutorials and guides JavaScript Guide Introduction Grammar and types Control flow and error handling Loops and iteration Functions Expressions and operators Numbers and strings Representing dates & times Regular expressions Indexed collections Keyed collections Working with objects Using classes Using promises JavaScript typed arrays Iterators and generators Resource management Internationalization JavaScript modules Intermediate Language overview JavaScript data structures Equality comparisons and sameness Enumerability and ownership of properties Closures Advanced Inheritance and the prototype chain Meta programming Memory Management References Built-in objects AggregateError Array ArrayBuffer AsyncDisposableStack AsyncFunction AsyncGenerator AsyncGeneratorFunction AsyncIterator Atomics BigInt BigInt64Array BigUint64Array Boolean DataView Date decodeURI() decodeURIComponent() DisposableStack encodeURI() encodeURIComponent() Error escape() Deprecated eval() EvalError FinalizationRegistry Float16Array Float32Array Float64Array Function Generator GeneratorFunction globalThis Infinity Int8Array Int16Array Int32Array InternalError Non-standard Intl isFinite() isNaN() Iterator JSON Map Math NaN Number Object parseFloat() parseInt() Promise Proxy RangeError ReferenceError Reflect RegExp Set SharedArrayBuffer String SuppressedError Symbol SyntaxError Temporal TypedArray TypeError Uint8Array Uint8ClampedArray Uint16Array Uint32Array undefined unescape() Deprecated URIError WeakMap WeakRef WeakSet Expressions & operators Addition (+) Addition assignment (+=) Assignment (=) async function expression async function* expression await Bitwise AND (&) Bitwise AND assignment (&=) Bitwise NOT (~) Bitwise OR (|) Bitwise OR assignment (|=) Bitwise XOR (^) Bitwise XOR assignment (^=) class expression Comma operator (,) Conditional (ternary) operator Decrement (--) delete Destructuring Division (/) Division assignment (/=) Equality (==) Exponentiation (**) Exponentiation assignment (**=) function expression function* expression Greater than (>) Greater than or equal (>=) Grouping operator ( ) import.meta import.meta.resolve() import() in Increment (++) Inequality (!=) instanceof Left shift (<<) Left shift assignment (<<=) Less than (<) Less than or equal (<=) Logical AND (&&) Logical AND assignment (&&=) Logical NOT (!) Logical OR (||) Logical OR assignment (||=) Multiplication (*) Multiplication assignment (*=) new new.target null Nullish coalescing assignment (??=) Nullish coalescing operator (??) Object initializer Operator precedence Optional chaining (?.) Property accessors Remainder (%) Remainder assignment (%=) Right shift (>>) Right shift assignment (>>=) Spread syntax (...) Strict equality (===) Strict inequality (!==) Subtraction (-) Subtraction assignment (-=) super this typeof Unary negation (-) Unary plus (+) Unsigned right shift (>>>) Unsigned right shift assignment (>>>=) void operator yield yield* Statements & declarations async function async function* await using Block statement break class const continue debugger do...while Empty statement export Expression statement for for await...of for...in for...of function function* if...else import Import attributes Labeled statement let return switch throw try...catch using var while with Deprecated Functions Arrow function expressions Default parameters get Method definitions Rest parameters set The arguments object [Symbol.iterator]() callee Deprecated length Classes constructor extends Private elements Public class fields static Static initialization blocks Regular expressions Backreference: \1, \2 Capturing group: (...) Character class escape: \d, \D, \w, \W, \s, \S Character class: [...], [^...] Character escape: \n, \u{...} Disjunction: | Input boundary assertion: ^, $ Literal character: a, b Lookahead assertion: (?=...), (?!...) Lookbehind assertion: (?<=...), (?<!...) Modifier: (?ims-ims:...) Named backreference: \k<name> Named capturing group: (?<name>...) Non-capturing group: (?:...) Quantifier: *, +, ?, {n}, {n,}, {n,m} Unicode character class escape: \p{...}, \P{...} Wildcard: . Word boundary assertion: \b, \B Errors AggregateError: No Promise in Promise.any was resolved Error: Permission denied to access property "x" InternalError: too much recursion RangeError: argument is not a valid code point RangeError: BigInt division by zero RangeError: BigInt negative exponent RangeError: form must be one of 'NFC', 'NFD', 'NFKC', or 'NFKD' RangeError: invalid array length RangeError: invalid date RangeError: precision is out of range RangeError: radix must be an integer RangeError: repeat count must be less than infinity RangeError: repeat count must be non-negative RangeError: x can't be converted to BigInt because it isn't an integer ReferenceError: "x" is not defined ReferenceError: assignment to undeclared variable "x" ReferenceError: can't access lexical declaration 'X' before initialization ReferenceError: must call super constructor before using 'this' in derived class constructor ReferenceError: super() called twice in derived class constructor SyntaxError: 'arguments'/'eval' can't be defined or assigned to in strict mode code SyntaxError: "0"-prefixed octal literals are deprecated SyntaxError: "use strict" not allowed in function with non-simple parameters SyntaxError: "x" is a reserved identifier SyntaxError: \ at end of pattern SyntaxError: a declaration in the head of a for-of loop can't have an initializer SyntaxError: applying the 'delete' operator to an unqualified name is deprecated SyntaxError: arguments is not valid in fields SyntaxError: await is only valid in async functions, async generators and modules SyntaxError: await/yield expression can't be used in parameter SyntaxError: cannot use `??` unparenthesized within `||` and `&&` expressions SyntaxError: character class escape cannot be used in class range in regular expression SyntaxError: continue must be inside loop SyntaxError: duplicate capture group name in regular expression SyntaxError: duplicate formal argument x SyntaxError: for-in loop head declarations may not have initializers SyntaxError: function statement requires a name SyntaxError: functions cannot be labelled SyntaxError: getter and setter for private name #x should either be both static or non-static SyntaxError: getter functions must have no arguments SyntaxError: identifier starts immediately after numeric literal SyntaxError: illegal character SyntaxError: import declarations may only appear at top level of a module SyntaxError: incomplete quantifier in regular expression SyntaxError: invalid assignment left-hand side SyntaxError: invalid BigInt syntax SyntaxError: invalid capture group name in regular expression SyntaxError: invalid character in class in regular expression SyntaxError: invalid class set operation in regular expression SyntaxError: invalid decimal escape in regular expression SyntaxError: invalid identity escape in regular expression SyntaxError: invalid named capture reference in regular expression SyntaxError: invalid property name in regular expression SyntaxError: invalid range in character class SyntaxError: invalid regexp group SyntaxError: invalid regular expression flag "x" SyntaxError: invalid unicode escape in regular expression SyntaxError: JSON.parse: bad parsing SyntaxError: label not found SyntaxError: missing : after property id SyntaxError: missing ) after argument list SyntaxError: missing ) after condition SyntaxError: missing ] after element list SyntaxError: missing } after function body SyntaxError: missing } after property list SyntaxError: missing = in const declaration SyntaxError: missing formal parameter SyntaxError: missing name after . operator SyntaxError: missing variable name SyntaxError: negated character class with strings in regular expression SyntaxError: new keyword cannot be used with an optional chain SyntaxError: nothing to repeat SyntaxError: numbers out of order in {} quantifier. SyntaxError: octal escape sequences can't be used in untagged template literals or in strict mode code SyntaxError: parameter after rest parameter SyntaxError: private fields can't be deleted SyntaxError: property name __proto__ appears more than once in object literal SyntaxError: raw bracket is not allowed in regular expression with unicode flag SyntaxError: redeclaration of formal parameter "x" SyntaxError: reference to undeclared private field or method #x SyntaxError: rest parameter may not have a default SyntaxError: return not in function SyntaxError: setter functions must have one argument SyntaxError: string literal contains an unescaped line break SyntaxError: super() is only valid in derived class constructors SyntaxError: tagged template cannot be used with optional chain SyntaxError: Unexpected '#' used outside of class body SyntaxError: Unexpected token SyntaxError: unlabeled break must be inside loop or switch SyntaxError: unparenthesized unary expression can't appear on the left-hand side of '**' SyntaxError: use of super property/member accesses only valid within methods or eval code within methods SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed TypeError: 'x' is not iterable TypeError: "x" is (not) "y" TypeError: "x" is not a constructor TypeError: "x" is not a function TypeError: "x" is not a non-null object TypeError: "x" is read-only TypeError: already executing generator TypeError: BigInt value can't be serialized in JSON TypeError: calling a builtin X constructor without new is forbidden TypeError: can't access/set private field or method: object is not the right class TypeError: can't assign to property "x" on "y": not an object TypeError: can't convert BigInt to number TypeError: can't convert x to BigInt TypeError: can't define property "x": "obj" is not extensible TypeError: can't delete non-configurable array element TypeError: can't redefine non-configurable property "x" TypeError: can't set prototype of this object TypeError: can't set prototype: it would cause a prototype chain cycle TypeError: cannot use 'in' operator to search for 'x' in 'y' TypeError: class constructors must be invoked with 'new' TypeError: cyclic object value TypeError: derived class constructor returned invalid value x TypeError: getting private setter-only property TypeError: Initializing an object twice is an error with private fields/methods TypeError: invalid 'instanceof' operand 'x' TypeError: invalid Array.prototype.sort argument TypeError: invalid assignment to const "x" TypeError: Iterator/AsyncIterator constructor can't be used directly TypeError: matchAll/replaceAll must be called with a global RegExp TypeError: More arguments needed TypeError: null/undefined has no properties TypeError: property "x" is non-configurable and can't be deleted TypeError: Reduce of empty array with no initial value TypeError: setting getter-only property "x" TypeError: WeakSet key/WeakMap value 'x' must be an object or an unregistered symbol TypeError: X.prototype.y called on incompatible type URIError: malformed URI sequence Warning: -file- is being assigned a //# sourceMappingURL, but already has one Warning: unreachable code after return statement Misc JavaScript technologies overview Execution model Lexical grammar Iteration protocols Strict mode Template literals Trailing commas Deprecated features Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://www.deloitte.com/us/en/insights/industry/retail-distribution.html?icid=disidenav_retail-distribution | Retail distribution | Deloitte Insights Please enable JavaScript to view the site. Skip to main content --> Deloitte Insights and the our research centers deliver proprietary research designed to help organizations turn their aspirations into action. DELOITTE INSIGHTS Home Spotlight Weekly Global Economic Outlook Tech Trends Human Capital Trends Digital Media Trends TMT Predictions FSI Predictions Topics Economics Environmental, Social, & Governance Operations Strategy Technology Workforce Industries More About Deloitte Insights Magazine Top 10 Reading Guide Videos DELOITTE RESEARCH CENTERS Cross-Industry Home Workforce Trends Enterprise Growth & Innovation Technology & Transformation Environmental & Social Issues Economics Home Consumer Spending Housing Business Investment Globalization & International Trade Fiscal & Monetary Policy Sustainability, Equity & Climate Labor Markets Prices & Inflation Consumer Home Automotive Consumer Products Food Retail, Wholesale & Distribution Hospitality & Airlines Transportation Energy & Industrials Home Aerospace & Defense Chemicals & Specialty Materials Engineering & Construction Industrial Manufacturing Mining & Metals Oil & Gas Power & Utilities Renewable Energy Financial Services Home Banking & Capital Markets Commercial Real Estate Insurance Investment Management Cross Financial Services Government & Public Services Home Defense, Security & Justice Government Health State & Local Government Whole of Government Transportation & Infrastructure Human Services Higher Education Life Sciences & Health Care Home Hospitals, Health Systems & Providers Pharmaceutical Manufacturers Health Plans & Payers Medtech & Health Tech Organizations Tech, Media & Telecom Home Technology Media & Entertainment Telecommunications Semiconductor Sports Consumer SECTORS Automotive Consumer Products Food Retail, Wholesale & Distribution Hospitality & Airlines Transportation TOPICS Consumer Sentiment & Behavior Industry Trends Future of Consumer Business Supply Chain RESEARCH CENTERS Cross-Industry Economics Consumer Energy & Industrials Financial Services Government & Public Services Life Sciences & Health Care Tech, Media & Telecom For You Welcome! For personalized content and settings, go to your My Deloitte Dashboard Latest Insights What do organizations need most in a disrupted, boundaryless age? More imagination. Article • 16-min read Recommendations TMT Predictions 2026: The AI gap narrows but persists Article • 9-min read About Deloitte Insights About Deloitte Insights Deloitte Insights Magazine, issue 33 Magazine Topics for you Business Strategy & Growth Leadership Operations Technology Workforce Economics Watch & Listen Dbriefs Stay informed on the issues impacting your business with Deloitte's live webcast series. Gain valuable insights and practical knowledge from our specialists while earning CPE credits. Deloitte Insights Videos Stay informed with content built for today’s business leaders. From data visualizations to expert commentary, our video content delivers concise, actionable information to help you lead with clarity in a complex world. Subscribe Deloitte Insights Newsletters Looking to stay on top of the latest news and trends? With MyDeloitte you'll never miss out on the information you need to lead. Simply link your email or social profile and select the newsletters and alerts that matter most to you. Deloitte Consumer Industry Center Retail Distribution Explore research and insights for retail distribution sector. --> Articles and multimedia FILTERS Show filters Hide filters CLOSE Topic — Select — APPLY FILTER Industry — Select — APPLY FILTER Type — Select — APPLY FILTER APPLY FILTER SORT Newest to oldest view edit filter(s) clear filter(s) SORT Newest to oldest view No results found. Try removing one of your filters. Sorry, no results found. 1 View All View 6 per page About the Deloitte Consumer Industry Center Consumers and the companies that serve them face a rapidly changing world, altering what, how, and where we buy products and services. Both consumers and businesses are buying into better products, services, and solutions to achieve their goals. The Deloitte Consumer Industry Center delivers insights to help automotive, consumer products, retail, transportation, hospitality, and services sector executives better understand their business environment, its direction, and the choices in front of them. Learn more Get in touch with our research team Stephen Rogers Managing Director Stephen Rogers Managing Director United States Steve is the managing director of Deloitte's Consumer Industry Center, Deloitte Services LP. He leads a team that conducts research to uncover new ways of thinking, working, and leading within the consumer industry through data and evidence driven analysis. With more than 20 years of experience within consulting and high tech, Steve is especially interested in the intersection of technology, consumers, and business. He is focused on how industry leaders can deliver better results and the strategies organizations use to adapt to accelerating change. stephenrogers@deloitte.com +1 475 277 9018 Lupine Skelly Retail, wholesale, and distribution research leader Lupine Skelly Retail, wholesale, and distribution research leader United States Lupine Skelly is a manager at Deloitte Services LP’s Consumer Industry Center and serves as the retail, wholesale and distribution research leader. She brings more than 15 years of retail market research experience to her work of uncovering actionable insights into emerging trends across the retail industry. Her research focuses on consumer behavior and how it relates to key retail events (such as back-to-school and holiday seasons), helping business leaders understand evolving market signals. lskelly@deloitte.com +1 206 716 7187 Ryan Robinson Automotive research leader | Director Ryan Robinson Automotive research leader | Director Canada Ryan is the research leader supporting the global Automotive sector for Deloitte's Consumer Industry Center. His primary focus is creating engaging, actionable insights to deepen the conversation around key trends and issues occurring across the global automotive sector landscape. ryanrobinson@deloitte.ca +1 647 502 9566 Maggie Rauch Transportation, hospitality, and services research leader | Deloitte Services LP Maggie Rauch Transportation, hospitality, and services research leader | Deloitte Services LP United States As Deloitte’s research manager for transportation, hospitality, and services, Maggie Rauch collaborates with firm leadership to design and execute research on the current state and future of the industry. She has a decade of experience as a travel industry subject matter expert and research team leader. magrauch@deloitte.com +1 212 436 5947 Justin Cook US consumer products research leader Justin Cook US consumer products research leader United States Justin Cook is the US consumer research leader at Deloitte and leads research for the consumer sector within Deloitte’s Consumer Industry Center, Deloitte Services LP. He conducts cross-sector research examining how factors such as inflation, value seeking, and trust influence consumer behavior and industry trends. juscook@deloitte.com +1 617 437 2071 My Deloitte Subscribe to receive personalized content Don't miss out on the information you need to lead. Subscribe today. Sign up Already joined? Log in Deloitte Insights and our research centers deliver proprietary research designed to help organizations turn their aspirations into action. DELOITTE INSIGHTS Home Deloitte Insights Magazine Top 10 Reading Guide Weekly Global Economic Outlook About Deloitte Insights DELOITTE RESEARCH CENTERS Cross-Industry Economics Consumer Energy & Industrials Financial Services Government & Public Services Life Sciences & Health Care Tech, Media & Telecom Learn about Deloitte’s offerings, people, and culture as a global provider of audit, assurance, consulting, financial advisory, risk advisory, tax, and related services. © 2026. See Terms of Use for more information. Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited, a UK private company limited by guarantee ("DTTL"), its network of member firms, and their related entities. DTTL and each of its member firms are legally separate and independent entities. DTTL (also referred to as "Deloitte Global") does not provide services to clients. In the United States, Deloitte refers to one or more of the US member firms of DTTL, their related entities that operate using the "Deloitte" name in the United States and their respective affiliates. Certain services may not be available to attest clients under the rules and regulations of public accounting. Please see www.deloitte.com/about to learn more about our global network of member firms. Terms of Use Privacy Data Privacy Framework Cookie Notice Cookie Settings Legal Information for Job Seekers Labor Condition Applications Do Not Sell or Share My Personal Information Please enable JavaScript to view the site. --> --> --> | 2026-01-13T08:48:26 |
https://www.refrens.com/ | Refrens | AI Accounting and ERP Platform ')"> Products ')"> Pricing India ')"> Login Sign Up ')"> Rated 4.8/5 by businesses worldwide AI Accounting and ERP Platform Trusted by 100,000+ businesses from 170+ countries. Try for Free Get a Demo ')"> ')"> Rated 4.8/5 by businesses worldwide AI Accounting and ERP Platform Trusted by 100,000+ businesses from 170+ countries. Try for Free Get a Demo Everything You Need To Grow Your Business Everything You Need To Grow Your Business Everything You Need To Grow Your Business Accounting Invoicing Compliance Payments Inventory Expenses Sales Vendors Accounting Automatically update your books when you make a sale or record a purchase, generate financial reports, automate bank reconciliation, access audit trails, create E-invoices & E-way Bills, generate GSTR-1 & GSTR-2B Reports, and automate GSTR-2B reconciliation. Try for Free Explore Accounting Accounting Automatically update your books when you make a sale or record a purchase, generate financial reports, automate bank reconciliation, access audit trails, create E-invoices & E-way Bills, generate GSTR-1 & GSTR-2B Reports, and automate GSTR-2B reconciliation. Try for Free Explore Accounting Accounting Automatically update your books when you make a sale or record a purchase, generate financial reports, automate bank reconciliation, access audit trails, create E-invoices & E-way Bills, generate GSTR-1 & GSTR-2B Reports, and automate GSTR-2B reconciliation. Try for Free Explore Accounting Invoicing Create, customise, and share invoices, quotations , and other receivable documents. Collect, record, and track payments. Automate recurring billing, payment reminders, journal entries, and inventory updates. Set up approval workflows. Integrate with third-party platforms Try for Free Explore Invoicing Invoicing Create, customise, and share invoices, quotations , and other receivable documents. Collect, record, and track payments. Automate recurring billing, payment reminders, journal entries, and inventory updates. Set up approval workflows. Integrate with third-party platforms Try for Free Explore Invoicing Compliance Create E-invoices , E-way Bills , generate GSTR-1 & GSTR-2B Reports, automate GSTR-2B reconciliation, access Audit trails, and auto-generate financial reports. Try for Free Get a Demo Compliance Create E-invoices , E-way Bills , generate GSTR-1 & GSTR-2B Reports, automate GSTR-2B reconciliation, access Audit trails, and auto-generate financial reports. Try for Free Get a Demo Payments Collect, record, and track payments. Send automated payment reminders. Auto-generate Payment Receipts. Automate bank reconciliation. Set up approval workflows. Generate ageing reports. Try for Free Get a Demo Payments Collect, record, and track payments. Send automated payment reminders. Auto-generate Payment Receipts. Automate bank reconciliation. Set up approval workflows. Generate ageing reports. Try for Free Get a Demo Inventory Auto-update inventory every time you make a sale or record a purchase, manage stock across multiple locations, track items batch-wise/serial-wise, monitor stock expiry, and keep track of inventory valuation and product-wise profitability. Try for Free Explore Inventory Management Inventory Auto-update inventory every time you make a sale or record a purchase, manage stock across multiple locations, track items batch-wise/serial-wise, monitor stock expiry, and keep track of inventory valuation and product-wise profitability. Try for Free Explore Inventory Management Expenses Record & track Purchases, Expenses, Employee Salaries, Reimbursements, and more. Set up approval workflows, create RFI links, and track vendor payments. Generate reports for Vendors, Payments, GSTR-2B, TDS, HSN, Vendor-ageing, and more. Try for Free Explore Expenses Management Expenses Record & track Purchases, Expenses, Employee Salaries, Reimbursements, and more. Set up approval workflows, create RFI links, and track vendor payments. Generate reports for Vendors, Payments, GSTR-2B, TDS, HSN, Vendor-ageing, and more. Try for Free Explore Expenses Management Sales Create lead capture forms, manage leads across multiple sales pipelines, centralise lead communication, integrate with IndiaMART/Meta, and generate sales reports to track the performance of your sales team & channels. Try for Free Explore Sales Management Sales Create lead capture forms, manage leads across multiple sales pipelines, centralise lead communication, integrate with IndiaMART/Meta, and generate sales reports to track the performance of your sales team & channels. Try for Free Explore Sales Management Vendors Manage vendor leads & onboarding, create vendor approval workflows, verify vendor KYC, create RFI/RFQ links, manage vendor payments, generate vendor-ageing reports, and more. Try for Free Get a Demo Vendors Manage vendor leads & onboarding, create vendor approval workflows, verify vendor KYC, create RFI/RFQ links, manage vendor payments, generate vendor-ageing reports, and more. Try for Free Get a Demo Accounting Invoicing Compliance Payments Inventory Expenses Sales Vendors Accounting Automatically update your books when you make a sale or record a purchase, generate financial reports, automate bank reconciliation, access audit trails, create E-invoices & E-way Bills, generate GSTR-1 & GSTR-2B Reports, and automate GSTR-2B reconciliation. Try for Free Explore Accounting Accounting Invoicing Compliance Payments Inventory Expenses Sales Vendors Accounting Automatically update your books when you make a sale or record a purchase, generate financial reports, automate bank reconciliation, access audit trails, create E-invoices & E-way Bills, generate GSTR-1 & GSTR-2B Reports, and automate GSTR-2B reconciliation. Try for Free Explore Accounting ')"> ')"> ')"> Smartest Entrepreneurs of India Backing Our Vision People who understand money, business, and all things Internet. People who understand money, business, & all things Internet. Akash Sinha Cashfree Payments Anupam Mittal Shaadi.com Vijay Shekhar Sharma Paytm Dinesh Agarwal IndiaMART Kunal Shah CRED — Along with Sidu Ponnappa (Ex-MD, Gojek India), founders of AngleList & many others — …along with FirstCheque, ITIGO Fund, AngelList and many others. Tailor Made For You Unicorn Startups, E-commerce Brands, B2B SaaS, D2C Brands, Wholesalers/Distributors, Service Agencies, Manufacturers, Internet Celebs, & Solopreneurs - All ❤️ Refrens! Unicorn Startups, E-commerce Brands, B2B SaaS, D2C Brands, Wholesalers/Distributors, Service Agencies, Manufacturers, Internet Celebs, & Solopreneurs All ❤️ Refrens! Highly Rated by Businesses Worldwide 4.6/5 Capterra ')"> ')"> 4.9/5 Product Hunt 4.7/5 G2 4.9/5 Trust Pilot 4.9/5 Software Suggest ')"> ')"> ')"> Simplified Workflow Tools Simple tools for freelancers, consultants, solopreneurs, and newly started businesses. ')"> Invoice Generator Create professional invoices with customizable templates for your business needs. Create Invoice ')"> GST Invoice Generator GST-compliant invoices, ensuring accuracy & tax regulation compliance Create GST Invoice ')"> Quotation Generator Quickly generate accurate quotations with detailed pricing and product information. Create Quotation ')"> Proforma Invoice Generator Generate detailed proforma invoices for cost estimation & transaction clarity. Create Proforma Invoice ')"> Delivery Challan Generator Simplify delivery documentation with a user-friendly delivery challan creation tool. Create Delivery Challan ')"> Purchase Order Generator Easily create and manage purchase orders for streamlined procurement. Create Purchase Order ')"> Invoice Generator Create professional invoices with customizable templates for your business needs. Create Invoice ')"> Purchase Order Generator Easily create and manage purchase orders for streamlined procurement. Create Purchase Order ')"> Quotation Generator Quickly generate accurate quotations with detailed pricing and product information. Create Quotation ')"> GST Invoice Generator GST-compliant invoices, ensuring accuracy & tax regulation compliance Create GST Invoice ')"> Delivery Challan Generator Simplify delivery documentation with a user-friendly delivery challan creation tool. Create Delivery Challan ')"> Proforma Invoice Generator Generate detailed proforma invoices for cost estimation & transaction clarity. Create Proforma Invoice Tailored Solutions From the day you start your business to the day you make it - we are here for you all the way. From the day you start your business to the day you make it we are here for you all the way. Large Enterprises Create professional invoices with all customizable templates for your business needs. GST Billing Software High Growth StartUps Simplify startup operations with cloud-based, inter-connected, and tailor-made solutions. Accounting for Startups Small Businesses Everything you need to manage your small business operations in one place. Accounting for Small Businesses Freelancers & Consultants Manage your freelance business operations with simple & highly affordable tools. Invoicing for Freelancers Chartered Accountant Become a Refrens Partner, get more clients for your CA firm, and access specialized benefits. Refrens for CAs Large Enterprises Create professional invoices with all customizable templates for your business needs. GST Billing Software High Growth StartUps Simplify startup operations with cloud-based, inter-connected, and tailor-made solutions. Accounting for Startups Small Businesses Everything you need to manage your small business operations in one place. Accounting for Small Businesses Freelancers & Consultants Manage your freelance business operations with simple & highly affordable tools. Invoicing for Freelancers Chartered Accountant Become a Refrens Partner, get more clients for your CA firm, and access specialized benefits. Refrens for CAs Introducing Freya Get real-time insights into your business finances with your personal AI agent Introducing Freya Get real-time insights into your business finances with your personal AI agent Introducing Freya Get real-time insights into your business finances with your personal AI agent Freya Your personal AI Agent Percentage of Invoiced Revenue from Discounts: Approximately 16.09% of invoiced revenue came from invoices that included a discount. Average Discount Percentage: The average discount percentage applied on those invoices was about 10.50% What percentage of invoiced revenue came from invoices that included a discount? What was the average discount percentage applied to those invoices? Ask Freya anything.. Get Access to Freya ')"> Freya Freya Your personal AI Agent Your personal AI Agent What percentage of invoiced revenue came from invoices that included a discount? What was the average discount percentage applied to those invoices? Percentage of Invoiced Revenue from Discounts: Approximately 16.09% of invoiced revenue came from invoices that included a discount. Average Discount Percentage: The average discount percentage applied on those invoices was about 10.50% Ask Freya anything.. Ask Freya anything.. ')"> Get Access to Freya ')"> Get Access to Freya ')"> Get Access to Freya ')"> Frequently Asked Questions (FAQs) What is Refrens? Refrens is a cloud-based, AI-powered, ISO certified platform that helps you manage your Invoicing, Accounting, Compliance, Payments, Expenses, Inventory, Sales, Clients, Vendors, and other business processes in one place. What is Refrens? Refrens is a cloud-based, AI-powered, ISO certified platform that helps you manage your Invoicing, Accounting, Compliance, Payments, Expenses, Inventory, Sales, Clients, Vendors, and other business processes in one place. What is Refrens? Refrens is a cloud-based, AI-powered, ISO certified platform that helps you manage your Invoicing, Accounting, Compliance, Payments, Expenses, Inventory, Sales, Clients, Vendors, and other business processes in one place. Will my data be safe with Refrens? As an ISO certified organization, we take utmost care when it comes to the security and privacy of your data. Read more about our privacy policy: https://www.refrens.com/privacy-policy Will my data be safe with Refrens? As an ISO certified organization, we take utmost care when it comes to the security and privacy of your data. Read more about our privacy policy: https://www.refrens.com/privacy-policy Will my data be safe with Refrens? As an ISO certified organization, we take utmost care when it comes to the security and privacy of your data. Read more about our privacy policy: https://www.refrens.com/privacy-policy How reliable is your system? What is your uptime? Refrens promises an uptime of 99% - which is among the best in the industry. Our robust system ensures that you are able to ensure your business operations without any interruptions. How reliable is your system? What is your uptime? Refrens promises an uptime of 99% - which is among the best in the industry. Our robust system ensures that you are able to ensure your business operations without any interruptions. How reliable is your system? What is your uptime? Refrens promises an uptime of 99% - which is among the best in the industry. Our robust system ensures that you are able to ensure your business operations without any interruptions. Can the software adapt & scale as my business grows ? Absolutely! Our software is designed to seamlessly adapt and scale alongside your business, ensuring that it meets your evolving needs at every stage of growth. We are also committed to continuously enhancing the software by rigorously adding new features, functionality, and improvements so that your business can always stay ahead of the curve. As your business expands, our software can accommodate an increasing number of users, manage larger volumes of data, and handle more complex tasks without compromising on performance or efficiency. We regularly update our software to incorporate new technological advancements, industry best practices, and customer feedback, ensuring that you always have access to the latest and most innovative solutions. Additionally, our cloud-based infrastructure offers unparalleled scalability and reliability, with the ability to adjust resources on-demand to cater to your business's specific needs. This means that you can be confident that our software will support your growth without any disruption or downtime. Can the software adapt & scale as my business grows ? Absolutely! Our software is designed to seamlessly adapt and scale alongside your business, ensuring that it meets your evolving needs at every stage of growth. We are also committed to continuously enhancing the software by rigorously adding new features, functionality, and improvements so that your business can always stay ahead of the curve. As your business expands, our software can accommodate an increasing number of users, manage larger volumes of data, and handle more complex tasks without compromising on performance or efficiency. We regularly update our software to incorporate new technological advancements, industry best practices, and customer feedback, ensuring that you always have access to the latest and most innovative solutions. Additionally, our cloud-based infrastructure offers unparalleled scalability and reliability, with the ability to adjust resources on-demand to cater to your business's specific needs. This means that you can be confident that our software will support your growth without any disruption or downtime. Can the software adapt & scale as my business grows ? Absolutely! Our software is designed to seamlessly adapt and scale alongside your business, ensuring that it meets your evolving needs at every stage of growth. We are also committed to continuously enhancing the software by rigorously adding new features, functionality, and improvements so that your business can always stay ahead of the curve. As your business expands, our software can accommodate an increasing number of users, manage larger volumes of data, and handle more complex tasks without compromising on performance or efficiency. We regularly update our software to incorporate new technological advancements, industry best practices, and customer feedback, ensuring that you always have access to the latest and most innovative solutions. Additionally, our cloud-based infrastructure offers unparalleled scalability and reliability, with the ability to adjust resources on-demand to cater to your business's specific needs. This means that you can be confident that our software will support your growth without any disruption or downtime. Refrens Internet Pvt. Ltd. +91 9104043036 +91 9104043036 care@refrens.com Global Australia Bahrain Bangladesh Canada Hong Kong India Indonesia Kenya Kuwait Malaysia Nigeria Oman Pakistan Qatar Philippines Saudi Arabia Singapore South Africa Srilanka UAE UK USA Vietnam Zimbabwe السعودية Company About Us Contact Us We are Hiring Blog Helpful Links Refrens Knowledge Base Pricing Become Refrens Partner Feedback Terms of Service Privacy Policy Refrens Android App Refrens IOS App Products Accounting Software GST Billing Software e-way Bill Software e-invoicing Software Invoicing Software Quotation Software Lead Management Software Sales CRM Lead to Quote Software Expense Management Software Invoicing API Online Invoice Generator Quotation Generator Quote and Invoice Software Pipeline Management Software Invoicing Software for Freelancers Indiamart CRM Integration Billing Software for Professional Services Invoicing Software for Consultants Inventory Management Software Services Hire Chartered Accountant Chartered Accountant in Mumbai Hire Freelancers Templates Invoice Templates GST Invoice Format Quotation Templates Proforma Invoice Templates Purchase Order Templates Quote Templates in Word & Excel Tax Invoice Templates Delivery Challan Format Refrens for CAs CA Elite Become Refrens Distributor Wallets Net Banking NEFT/IMPS Made with , & in Bengaluru This site is protected by reCAPTHA & the Google Privacy Policy and Terms of Service apply Made with , & in Bengaluru | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors | CSS selectors - CSS | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web CSS Reference Selectors Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 中文 (简体) CSS selectors CSS selectors are patterns used in CSS rules to target and select specific elements for styling. Note: This page is an index of all selectors in CSS. The CSS selectors page introduces the module that defines some, but not all, of these selectors. For example, to style paragraphs, you will use the p type selector to select all <p> elements and apply a style to them: css /* Set font size on all <p> elements */ p { font-size: 12px; color: rebeccapurple; } In this article Syntax Index of selectors Specifications See also Syntax css /* Select elements and apply styles */ selector { property: value; } Index of selectors & nesting selector Attribute selectors Class selectors ID selectors Keyframe selectors Namespace separator ( | ) Pseudo-class selectors Pseudo-element selectors Selector list Type selectors Universal selectors Specifications Specification Selectors Level 4 Check the pseudo-classes and pseudo-elements pages for their respective specification tables. See also CSS selectors module CSS selector structure CSS combinators Selector list Selectors and combinators CSS pseudo-elements module CSS nesting module Specificity Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jan 8, 2026 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar CSS Guides Modules Anchor positioning Animations Backgrounds and borders Basic user interface Borders and box decorations Box alignment Box model Box sizing Cascading and inheritance Color adjustment Colors Compositing and blending Conditional rules Containment Counter styles CSSOM view Custom functions and mixins Custom highlight API Custom properties for cascading variables Display Easing functions Environment variables Filter effects Flexible box layout Font loading Fonts Fragmentation Generated content Grid layout Images Inline layout Lists and counters Logical properties and values Masking Media queries Motion path Multi-column layout Namespaces Nesting Overflow Overscroll behavior Paged media Positioned layout Properties and values API Pseudo-elements Round display Ruby layout Scoping Scroll anchoring Scroll snap Scroll-driven animations Scrollbars styling Selectors Shadow parts Shapes Syntax Table Text Text decoration Transforms Transitions Values and units View transitions Viewport Writing modes Anchor positioning Using anchor positioning Handling overflow Animations Animatable properties Using animations Backgrounds and borders Using multiple backgrounds Resizing background images Scaling SVG backgrounds Box alignment Overview In block layout In flexbox In grid layout In multi-column layout Box model Introduction Margin collapsing Box sizing Aspect ratios Cascade Introduction Inheritance Specificity Property value processing Shorthand properties Cascading variables Using custom properties Colors Applying color Color values Using relative colors Using color wisely Accessibility: Colors and luminance Accessibility: Color contrast Columns Basic concepts Styling columns Using multi-column layouts Spanning and balancing columns Handling overflow Handling content breaks Conditional rules Using feature queries Using container scroll-state queries Containment Container queries Using containment Using container size and style queries CSSOM view Coordinate systems (API) Viewport concepts Custom functions and mixins Using CSS custom functions Display Block and inline layout Flow layout Flow layout and overflow Flow layout and writing modes In flow and out of flow Layout and the containing block Formatting contexts Block formatting context Inline formatting context Using multi-keyword syntax Visual formatting model Environment variables Using environment variables Filter effects Using filter effects Flexbox Basic concepts Flexbox and other layouts Aligning flex items Ordering flex items Controlling flex item ratios Wrapping flex items Typical use cases Fonts OpenType features Variable fonts WOFF Grid Basic concepts Grid and other layouts Using line-based placement Grid template areas Using named grid lines Using auto-placement Aligning items Logical values and writing modes Grid layout and accessibility Common grid layouts Subgrid Masonry layout Experimental Images Using gradients Using object-view-box Styling replaced elements Implementing image sprites Lists and counters Using counters Indenting lists Logical properties Basic concepts For floating and positioning For margins, borders, and padding For sizing Masking Introduction Clipping Multiple masks Mask properties Media queries Using media queries For accessibility Testing Printing Nesting style rules Nesting at-rules Nesting and specificity Using nesting Overflow Creating carousels Positioning Stacking context Example 1 Example 2 Example 3 Stacking floating elements Understanding z-index Using z-index Stacking without z-index Scroll anchoring Overview Scroll-driven animations Scroll-driven animation timelines Scroll snap Basic concepts Using scroll snap events Selectors Selectors and combinators Selector structure Privacy and :visited Using :target Shapes Overview Box-value shapes Image-based shapes Using shape-outside Syntax Introduction Comments At-rules Error handling Text Wrapping and breaking text Handling whitespace Text decoration Text shadows Transforms Using transforms Transitions Using transitions Values and units Value definition syntax Numeric data types Textual data types Using math functions Using typed arithmetic Writing modes Introduction Vertical form controls How to Layout cookbook Media objects Column layouts Center an element Sticky footers Split navigation Breadcrumb navigation List group with badges Pagination Card Grid wrapper Contribute a recipe Cookbook template Tools Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator Reference Properties -moz-* -moz-float-edge Non-standard Deprecated -moz-force-broken-image-icon Non-standard Deprecated -moz-orient Non-standard -moz-user-focus Non-standard Deprecated -moz-user-input Non-standard Deprecated -webkit-* -webkit-border-before Non-standard -webkit-box-reflect Non-standard -webkit-mask-box-image Non-standard -webkit-mask-composite Non-standard -webkit-mask-position-x Non-standard -webkit-mask-position-y Non-standard -webkit-mask-repeat-x Non-standard -webkit-mask-repeat-y Non-standard -webkit-tap-highlight-color Non-standard -webkit-text-fill-color -webkit-text-security Non-standard -webkit-text-stroke -webkit-text-stroke-color -webkit-text-stroke-width -webkit-touch-callout Non-standard Custom properties (--*): CSS variables accent-color align-* align-content align-items align-self alignment-baseline all anchor-name anchor-scope animation-* animation animation-composition animation-delay animation-direction animation-duration animation-fill-mode animation-iteration-count animation-name animation-play-state animation-range animation-range-end animation-range-start animation-timeline animation-timing-function appearance aspect-ratio backdrop-filter backface-visibility background-* background background-attachment background-blend-mode background-clip background-color background-image background-origin background-position background-position-x background-position-y background-repeat background-size baseline-source block-size border-* border border-block border-block-color border-block-end border-block-end-color border-block-end-style border-block-end-width border-block-start border-block-start-color border-block-start-style border-block-start-width border-block-style border-block-width border-bottom border-bottom-color border-bottom-left-radius border-bottom-right-radius border-bottom-style border-bottom-width border-collapse border-color border-end-end-radius border-end-start-radius border-image border-image-outset border-image-repeat border-image-slice border-image-source border-image-width border-inline border-inline-color border-inline-end border-inline-end-color border-inline-end-style border-inline-end-width border-inline-start border-inline-start-color border-inline-start-style border-inline-start-width border-inline-style border-inline-width border-left border-left-color border-left-style border-left-width border-radius border-right border-right-color border-right-style border-right-width border-spacing border-start-end-radius border-start-start-radius border-style border-top border-top-color border-top-left-radius border-top-right-radius border-top-style border-top-width border-width bottom box-* box-align Non-standard Deprecated box-decoration-break box-direction Non-standard Deprecated box-flex Non-standard Deprecated box-flex-group Non-standard Deprecated box-lines Non-standard Deprecated box-ordinal-group Non-standard Deprecated box-orient Non-standard Deprecated box-pack Non-standard Deprecated box-shadow box-sizing break-* break-after break-before break-inside caption-side caret-* caret Experimental caret-animation Experimental caret-color caret-shape Experimental clear clip-* clip Deprecated clip-path clip-rule color-* color color-interpolation color-interpolation-filters color-scheme column-* column-count column-fill column-gap column-rule column-rule-color column-rule-style column-rule-width column-span column-width columns contain-* contain contain-intrinsic-block-size contain-intrinsic-height contain-intrinsic-inline-size contain-intrinsic-size contain-intrinsic-width container-* container container-name container-type content content-visibility corner-* corner-block-end-shape Experimental corner-block-start-shape Experimental corner-bottom-left-shape Experimental corner-bottom-right-shape Experimental corner-bottom-shape Experimental corner-end-end-shape Experimental corner-end-start-shape Experimental corner-inline-end-shape Experimental corner-inline-start-shape Experimental corner-left-shape Experimental corner-right-shape Experimental corner-shape Experimental corner-start-end-shape Experimental corner-start-start-shape Experimental corner-top-left-shape Experimental corner-top-right-shape Experimental corner-top-shape Experimental counter-* counter-increment counter-reset counter-set cursor cx cy d direction display dominant-baseline dynamic-range-limit empty-cells field-sizing fill-* fill fill-opacity fill-rule filter flex-* flex flex-basis flex-direction flex-flow flex-grow flex-shrink flex-wrap float flood-color flood-opacity font-* font font-family font-feature-settings font-kerning font-language-override font-optical-sizing font-palette font-size font-size-adjust font-smooth Non-standard font-stretch Deprecated font-style font-synthesis font-synthesis-position Experimental font-synthesis-small-caps font-synthesis-style font-synthesis-weight font-variant font-variant-alternates font-variant-caps font-variant-east-asian font-variant-emoji font-variant-ligatures font-variant-numeric font-variant-position font-variation-settings font-weight forced-color-adjust gap grid-* grid grid-area grid-auto-columns grid-auto-flow grid-auto-rows grid-column grid-column-end grid-column-start grid-row grid-row-end grid-row-start grid-template grid-template-areas grid-template-columns grid-template-rows hanging-punctuation height hyphenate-character hyphenate-limit-chars hyphens image-* image-orientation image-rendering image-resolution Experimental initial-letter inline-size inset-* inset inset-block inset-block-end inset-block-start inset-inline inset-inline-end inset-inline-start interactivity Experimental interest-* interest-delay Experimental interest-delay-end Experimental interest-delay-start Experimental interpolate-size Experimental isolation justify-* justify-content justify-items justify-self left letter-spacing lighting-color line-* line-break line-clamp line-height line-height-step Experimental list-* list-style list-style-image list-style-position list-style-type margin-* margin margin-block margin-block-end margin-block-start margin-bottom margin-inline margin-inline-end margin-inline-start margin-left margin-right margin-top margin-trim Experimental marker-* marker marker-end marker-mid marker-start mask-* mask mask-border mask-border-mode mask-border-outset mask-border-repeat mask-border-slice mask-border-source mask-border-width mask-clip mask-composite mask-image mask-mode mask-origin mask-position mask-repeat mask-size mask-type math-* math-depth math-shift math-style max-* max-block-size max-height max-inline-size max-width min-* min-block-size min-height min-inline-size min-width mix-blend-mode object-* object-fit object-position object-view-box Experimental offset-* offset offset-anchor offset-distance offset-path offset-position offset-rotate opacity order orphans outline-* outline outline-color outline-offset outline-style outline-width overflow-* overflow overflow-anchor overflow-block overflow-clip-margin overflow-inline overflow-wrap overflow-x overflow-y overlay Experimental overscroll-* overscroll-behavior overscroll-behavior-block overscroll-behavior-inline overscroll-behavior-x overscroll-behavior-y padding-* padding padding-block padding-block-end padding-block-start padding-bottom padding-inline padding-inline-end padding-inline-start padding-left padding-right padding-top page-* page page-break-after Deprecated page-break-before Deprecated page-break-inside Deprecated paint-order perspective perspective-origin place-* place-content place-items place-self pointer-events position-* position position-anchor position-area position-try position-try-fallbacks position-try-order position-visibility print-color-adjust quotes r reading-flow Experimental reading-order Experimental resize right rotate row-gap ruby-* ruby-align ruby-overhang ruby-position rx ry scale scroll-* scroll-behavior scroll-margin scroll-margin-block scroll-margin-block-end scroll-margin-block-start scroll-margin-bottom scroll-margin-inline scroll-margin-inline-end scroll-margin-inline-start scroll-margin-left scroll-margin-right scroll-margin-top scroll-marker-group Experimental scroll-padding scroll-padding-block scroll-padding-block-end scroll-padding-block-start scroll-padding-bottom scroll-padding-inline scroll-padding-inline-end scroll-padding-inline-start scroll-padding-left scroll-padding-right scroll-padding-top scroll-snap-align scroll-snap-stop scroll-snap-type scroll-target-group Experimental scroll-timeline scroll-timeline-axis scroll-timeline-name scrollbar-* scrollbar-color scrollbar-gutter scrollbar-width shape-* shape-image-threshold shape-margin shape-outside shape-rendering speak-as Experimental stop-color stop-opacity stroke-* stroke stroke-dasharray stroke-dashoffset stroke-linecap stroke-linejoin stroke-miterlimit stroke-opacity stroke-width tab-size table-layout text-* text-align text-align-last text-anchor text-autospace text-box text-box-edge text-box-trim text-combine-upright text-decoration text-decoration-color text-decoration-inset Experimental text-decoration-line text-decoration-skip Experimental text-decoration-skip-ink text-decoration-style text-decoration-thickness text-emphasis text-emphasis-color text-emphasis-position text-emphasis-style text-indent text-justify text-orientation text-overflow text-rendering text-shadow text-size-adjust Experimental text-spacing-trim Experimental text-transform text-underline-offset text-underline-position text-wrap text-wrap-mode text-wrap-style timeline-scope top touch-action transform-* transform transform-box transform-origin transform-style transition-* transition transition-behavior transition-delay transition-duration transition-property transition-timing-function translate unicode-bidi user-modify Non-standard Deprecated user-select vector-effect vertical-align view-* view-timeline view-timeline-axis view-timeline-inset view-timeline-name view-transition-class view-transition-name visibility white-space white-space-collapse widows width will-change word-break word-spacing writing-mode x y z-index zoom Selectors & nesting selector Attribute selectors Class selectors ID selectors Keyframe selectors Namespace separator Selector list Type selectors Universal selectors Combinators Child combinator Column combinator Experimental Descendant combinator Next-sibling combinator Subsequent-sibling combinator Pseudo-classes :-moz-* :-moz-broken Non-standard Deprecated :-moz-drag-over Non-standard :-moz-first-node Experimental Non-standard :-moz-handler-blocked Non-standard :-moz-handler-crashed Non-standard :-moz-handler-disabled Non-standard :-moz-last-node Experimental Non-standard :-moz-loading Non-standard :-moz-locale-dir(ltr) Non-standard :-moz-locale-dir(rtl) Non-standard :-moz-only-whitespace Non-standard :-moz-submit-invalid Non-standard :-moz-suppressed Non-standard :-moz-user-disabled Non-standard :-moz-window-inactive Non-standard :active-* :active :active-view-transition :active-view-transition-type() :any-link :autofill :blank Experimental :buffering :checked :current Experimental :default :defined :dir() :disabled :empty :enabled :first-* :first :first-child :first-of-type :focus-* :focus :focus-visible :focus-within :fullscreen :future :has-slotted :has() :heading Experimental :heading() Experimental :host :host-context() Deprecated :host() :hover :in-range :indeterminate :interest-source Experimental :interest-target Experimental :invalid :is() :lang() :last-child :last-of-type :left :link :local-link Experimental :modal :muted :not() :nth-* :nth-child() :nth-last-child() :nth-last-of-type() :nth-of-type() :only-child :only-of-type :open :optional :out-of-range :past :paused :picture-in-picture :placeholder-shown :playing :popover-open :read-only :read-write :required :right :root :scope :seeking :stalled :state() :target-* :target :target-after Experimental :target-before Experimental :target-current Experimental :user-invalid :user-valid :valid :visited :volume-locked :where() Pseudo-elements ::-moz-* ::-moz-color-swatch Non-standard ::-moz-focus-inner Non-standard Deprecated ::-moz-list-bullet Experimental Non-standard ::-moz-list-number Experimental Non-standard ::-moz-meter-bar Non-standard ::-moz-progress-bar Experimental Non-standard ::-moz-range-progress Non-standard ::-moz-range-thumb Non-standard ::-moz-range-track Non-standard ::-webkit-* ::-webkit-inner-spin-button Non-standard ::-webkit-meter-bar Non-standard Deprecated ::-webkit-meter-even-less-good-value Non-standard ::-webkit-meter-inner-element Non-standard ::-webkit-meter-optimum-value Non-standard ::-webkit-meter-suboptimum-value Non-standard ::-webkit-progress-bar Non-standard ::-webkit-progress-inner-element Non-standard ::-webkit-progress-value Non-standard ::-webkit-scrollbar Non-standard ::-webkit-search-cancel-button Non-standard ::-webkit-search-results-button Non-standard ::-webkit-slider-runnable-track Non-standard ::-webkit-slider-thumb Non-standard ::after ::backdrop ::before ::checkmark Experimental ::column Experimental ::cue ::details-content ::file-selector-button ::first-letter ::first-line ::grammar-error ::highlight() ::marker ::part() ::picker-icon Experimental ::picker() Experimental ::placeholder ::scroll-* ::scroll-button() Experimental ::scroll-marker Experimental ::scroll-marker-group Experimental ::selection ::slotted() ::spelling-error ::target-text ::view-* ::view-transition ::view-transition-group() ::view-transition-image-pair() ::view-transition-new() ::view-transition-old() At-rules @charset @color-profile @container @counter-style @custom-media Experimental @document Non-standard Deprecated @font-face @font-feature-values @font-palette-values @function Experimental @import @keyframes @layer @media @namespace @page @position-try @property @scope @starting-style @supports @view-transition Values !important fit-content inherit initial max-content min-content revert revert-layer rule-list unset Types <absolute-size> <alpha-value> <angle-percentage> <angle> <axis> <baseline-position> <basic-shape> <blend-mode> <box-edge> <calc-keyword> <calc-sum> <color-interpolation-method> <color> <content-distribution> <content-position> <corner-shape-value> Experimental <custom-ident> <dashed-function> Experimental <dashed-ident> <dimension> <display-box> <display-inside> <display-internal> <display-legacy> <display-listitem> <display-outside> <easing-function> <filter-function> <flex> <frequency-percentage> <frequency> <generic-family> <gradient> <hex-color> <hue-interpolation-method> <hue> <ident> <image> <integer> <length-percentage> <length> <line-style> <named-color> <number> <overflow-position> <overflow> <percentage> <position-area> <position> <ratio> <relative-size> <resolution> <self-position> <shape> Deprecated <string> <system-color> <text-edge> <time-percentage> <time> <timeline-range-name> <transform-function> <url> Functions -moz-image-rect Non-standard Deprecated abs() acos() anchor-size() anchor() asin() atan() atan2() attr() blur() brightness() calc-size() Experimental calc() circle() clamp() color-mix() color() conic-gradient() contrast-color() contrast() cos() counter() counters() cross-fade() cubic-bezier() device-cmyk() drop-shadow() dynamic-range-limit-mix() Experimental element() Experimental ellipse() env() exp() fit-content() grayscale() hsl() hue-rotate() hwb() hypot() if() Experimental image-set() image() inset() invert() lab() lch() light-dark() linear-gradient() linear() log() matrix() matrix3d() max() min() minmax() mod() oklab() oklch() opacity() paint() path() perspective() polygon() pow() progress() radial-gradient() ray() rect() rem() repeat() repeating-conic-gradient() repeating-linear-gradient() repeating-radial-gradient() rgb() rotate() rotate3d() rotateX() rotateY() rotateZ() round() saturate() scale() scale3d() scaleX() scaleY() scaleZ() sepia() shape() sibling-count() sibling-index() sign() sin() skew() skewX() skewY() sqrt() steps() superellipse() Experimental symbols() tan() translate() translate3d() translateX() translateY() translateZ() type() Experimental url() var() xywh() Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/play | Playground | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Playground Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Playground Format Run Share Clear HTML CSS JAVASCRIPT Console Exit modal Share Markdown Copy markdown to clipboard Share your code via Permalink Exit modal Report this malicious or inappropriate shared playground. Can you please share some details on what's wrong with this content: Cancel Report Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes | HTML attribute reference - HTML | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTML Reference Attributes Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) HTML attribute reference Elements in HTML have attributes ; these are additional values that configure the elements or adjust their behavior in various ways to meet the criteria the users want. In this article Attribute list Content versus IDL attributes Boolean Attributes Event handler attributes See also Attribute list Attribute Name Elements Description accept <form> , <input> List of types the server accepts, typically a file type. accept-charset <form> The character set, which if provided must be "UTF-8" . accesskey Global attribute Keyboard shortcut to activate or add focus to the element. action <form> The URI of a program that processes the information submitted via the form. align Deprecated <caption> , <col> , <colgroup> , <hr> , <iframe> , <img> , <table> , <tbody> , <td> , <tfoot> , <th> , <thead> , <tr> Specifies the horizontal alignment of the element. allow <iframe> Specifies a feature-policy for the iframe. alpha <input> Allow the user to select a color's opacity on a type="color" input. alt <area> , <img> , <input> Alternative text in case an image can't be displayed. as <link> Specifies the type of content being loaded by the link. async <script> Executes the script asynchronously. autocapitalize Global attribute Sets whether input is automatically capitalized when entered by user autocomplete <form> , <input> , <select> , <textarea> Indicates whether controls in this form can by default have their values automatically completed by the browser. autoplay <audio> , <video> The audio or video should play as soon as possible. background <body> , <table> , <td> , <th> Specifies the URL of an image file. Note: Although browsers and email clients may still support this attribute, it is obsolete. Use CSS background-image instead. bgcolor <body> , <col> , <colgroup> , <marquee> , <table> , <tbody> , <tfoot> , <td> , <th> , <tr> Background color of the element. Note: This is a legacy attribute. Please use the CSS background-color property instead. border <img> , <object> , <table> The border width. Note: This is a legacy attribute. Please use the CSS border property instead. capture <input> From the Media Capture specification , specifies a new file can be captured. charset <meta> Declares the character encoding of the page or script. checked <input> Indicates whether the element should be checked on page load. cite <blockquote> , <del> , <ins> , <q> Contains a URI which points to the source of the quote or change. class Global attribute Often used with CSS to style elements with common properties. color <font> , <hr> This attribute sets the text color using either a named color or a color specified in the hexadecimal #RRGGBB format. Note: This is a legacy attribute. Please use the CSS color property instead. colorspace <input> Defines the color space that is used by a type="color" input. cols <textarea> Defines the number of columns in a textarea. colspan <td> , <th> The colspan attribute defines the number of columns a cell should span. content <meta> A value associated with http-equiv or name depending on the context. contenteditable Global attribute Indicates whether the element's content is editable. controls <audio> , <video> Indicates whether the browser should show playback controls to the user. coords <area> A set of values specifying the coordinates of the hot-spot region. crossorigin <audio> , <img> , <link> , <script> , <video> How the element handles cross-origin requests csp Experimental <iframe> Specifies the Content Security Policy that an embedded document must agree to enforce upon itself. data <object> Specifies the URL of the resource. data-* Global attribute Lets you attach custom attributes to an HTML element. datetime <del> , <ins> , <time> Indicates the date and time associated with the element. decoding <img> Indicates the preferred method to decode the image. default <track> Indicates that the track should be enabled unless the user's preferences indicate something different. defer <script> Indicates that the script should be executed after the page has been parsed. dir Global attribute Defines the text direction. Allowed values are ltr (Left-To-Right) or rtl (Right-To-Left) dirname <input> , <textarea> disabled <button> , <fieldset> , <input> , <optgroup> , <option> , <select> , <textarea> Indicates whether the user can interact with the element. download <a> , <area> Indicates that the hyperlink is to be used for downloading a resource. draggable Global attribute Defines whether the element can be dragged. enctype <form> Defines the content type of the form data when the method is POST. enterkeyhint <textarea> , contenteditable The enterkeyhint specifies what action label (or icon) to present for the enter key on virtual keyboards. The attribute can be used with form controls (such as the value of textarea elements), or in elements in an editing host (e.g., using contenteditable attribute). elementtiming <img> , <image> elements inside an <svg> , poster images of <video> elements, elements which have a background-image , and elements containing text nodes, such as a <p> Indicates that an element is flagged for tracking by PerformanceObserver objects using the "element" type. For more details, see the PerformanceElementTiming interface. fetchpriority <img> , <link> , <script> Signals that fetching a particular image early in the loading process has more or less impact on user experience than a browser can reasonably infer when assigning an internal priority. for <label> , <output> Describes elements which belongs to this one. form <button> , <fieldset> , <input> , <object> , <output> , <select> , <textarea> Indicates the form that is the owner of the element. formaction <input> , <button> Indicates the action of the element, overriding the action defined in the <form> . formenctype <button> , <input> If the button/input is a submit button (e.g., type="submit" ), this attribute sets the encoding type to use during form submission. If this attribute is specified, it overrides the enctype attribute of the button's form owner. formmethod <button> , <input> If the button/input is a submit button (e.g., type="submit" ), this attribute sets the submission method to use during form submission ( GET , POST , etc.). If this attribute is specified, it overrides the method attribute of the button's form owner. formnovalidate <button> , <input> If the button/input is a submit button (e.g., type="submit" ), this boolean attribute specifies that the form is not to be validated when it is submitted. If this attribute is specified, it overrides the novalidate attribute of the button's form owner. formtarget <button> , <input> If the button/input is a submit button (e.g., type="submit" ), this attribute specifies the browsing context (for example, tab, window, or inline frame) in which to display the response that is received after submitting the form. If this attribute is specified, it overrides the target attribute of the button's form owner. headers <td> , <th> IDs of the <th> elements which applies to this element. height <canvas> , <embed> , <iframe> , <img> , <input> , <object> , <video> Specifies the height of elements listed here. For all other elements, use the CSS height property. Note: In some instances, such as <div> , this is a legacy attribute, in which case the CSS height property should be used instead. hidden Global attribute Prevents rendering of given element, while keeping child elements, e.g. script elements, active. high <meter> Indicates the lower bound of the upper range. href <a> , <area> , <base> , <link> The URL of a linked resource. hreflang <a> , <link> Specifies the language of the linked resource. http-equiv <meta> Defines a pragma directive. id Global attribute Often used with CSS to style a specific element. The value of this attribute must be unique. integrity <link> , <script> Specifies a Subresource Integrity value that allows browsers to verify what they fetch. inputmode <textarea> , contenteditable Provides a hint as to the type of data that might be entered by the user while editing the element or its contents. The attribute can be used with form controls (such as the value of textarea elements), or in elements in an editing host (e.g., using contenteditable attribute). ismap <img> Indicates that the image is part of a server-side image map. itemprop Global attribute kind <track> Specifies the kind of text track. label <optgroup> , <option> , <track> Specifies a user-readable title of the element. lang Global attribute Defines the language used in the element. language Deprecated <script> Defines the script language used in the element. loading <img> , <iframe> Indicates if the element should be loaded lazily ( loading="lazy" ) or loaded immediately ( loading="eager" ). list <input> Identifies a list of pre-defined options to suggest to the user. loop <audio> , <marquee> , <video> Indicates whether the media should start playing from the start when it's finished. low <meter> Indicates the upper bound of the lower range. max <input> , <meter> , <progress> Indicates the maximum value allowed. maxlength <input> , <textarea> Defines the maximum number of characters allowed in the element. minlength <input> , <textarea> Defines the minimum number of characters allowed in the element. media <a> , <area> , <link> , <source> , <style> Specifies a hint of the media for which the linked resource was designed. method <form> Defines which HTTP method to use when submitting the form. Can be GET (default) or POST . min <input> , <meter> Indicates the minimum value allowed. multiple <input> , <select> Indicates whether multiple values can be entered in an input of the type email or file . muted <audio> , <video> Indicates whether the audio will be initially silenced on page load. name <button> , <form> , <fieldset> , <iframe> , <input> , <object> , <output> , <select> , <textarea> , <map> , <meta> , <param> Name of the element. For example used by the server to identify the fields in form submits. novalidate <form> This attribute indicates that the form shouldn't be validated when submitted. open <details> , <dialog> Indicates whether the contents are currently visible (in the case of a <details> element) or whether the dialog is active and can be interacted with (in the case of a <dialog> element). optimum <meter> Indicates the optimal numeric value. pattern <input> Defines a regular expression which the element's value will be validated against. ping <a> , <area> The ping attribute specifies a space-separated list of URLs to be notified if a user follows the hyperlink. placeholder <input> , <textarea> Provides a hint to the user of what can be entered in the field. playsinline <video> A Boolean attribute indicating that the video is to be played "inline"; that is, within the element's playback area. Note that the absence of this attribute does not imply that the video will always be played in fullscreen. poster <video> A URL indicating a poster frame to show until the user plays or seeks. preload <audio> , <video> Indicates whether the whole resource, parts of it or nothing should be preloaded. readonly <input> , <textarea> Indicates whether the element can be edited. referrerpolicy <a> , <area> , <iframe> , <img> , <link> , <script> Specifies which referrer is sent when fetching the resource. rel <a> , <area> , <link> Specifies the relationship of the target object to the link object. required <input> , <select> , <textarea> Indicates whether this element is required to fill out or not. reversed <ol> Indicates whether the list should be displayed in a descending order instead of an ascending order. role Global attribute Defines an explicit role for an element for use by assistive technologies. rows <textarea> Defines the number of rows in a text area. rowspan <td> , <th> Defines the number of rows a table cell should span over. sandbox <iframe> Stops a document loaded in an iframe from using certain features (such as submitting forms or opening new windows). scope <th> Defines the cells that the header test (defined in the th element) relates to. selected <option> Defines a value which will be selected on page load. shape <a> , <area> size <input> , <select> Defines the width of the element (in pixels). If the element's type attribute is text or password then it's the number of characters. sizes <link> , <img> , <source> slot Global attribute Assigns a slot in a shadow DOM shadow tree to an element. span <col> , <colgroup> spellcheck Global attribute Indicates whether spell checking is allowed for the element. src <audio> , <embed> , <iframe> , <img> , <input> , <script> , <source> , <track> , <video> The URL of the embeddable content. srcdoc <iframe> srclang <track> srcset <img> , <source> One or more responsive image candidates. start <ol> Defines the first number if other than 1. step <input> style Global attribute Defines CSS styles which will override styles previously set. summary Deprecated <table> tabindex Global attribute Overrides the browser's default tab order and follows the one specified instead. target <a> , <area> , <base> , <form> Specifies where to open the linked document (in the case of an <a> element) or where to display the response received (in the case of a <form> element) title Global attribute Text to be displayed in a tooltip when hovering over the element. translate Global attribute Specify whether an element's attribute values and the values of its Text node children are to be translated when the page is localized, or whether to leave them unchanged. type <button> , <input> , <embed> , <object> , <ol> , <script> , <source> , <style> , <menu> , <link> Defines the type of the element. usemap <img> , <input> , <object> value <button> , <data> , <input> , <li> , <meter> , <option> , <progress> , <param> Defines a default value which will be displayed in the element on page load. width <canvas> , <embed> , <iframe> , <img> , <input> , <object> , <video> For the elements listed here, this establishes the element's width. Note: For all other instances, such as <div> , this is a legacy attribute, in which case the CSS width property should be used instead. wrap <textarea> Indicates whether the text should be wrapped. Content versus IDL attributes In HTML, most attributes have two faces: the content attribute and the IDL (Interface Definition Language) attribute . The content attribute is the attribute as you set it from the content (the HTML code) and you can set it or get it via element.setAttribute() or element.getAttribute() . The content attribute is always a string even when the expected value should be an integer. For example, to set an <input> element's maxlength to 42 using the content attribute, you have to call setAttribute("maxlength", "42") on that element. The IDL attribute is also known as a JavaScript property. These are the attributes you can read or set using JavaScript properties like element.foo . The IDL attribute is always going to use (but might transform) the underlying content attribute to return a value when you get it and is going to save something in the content attribute when you set it. In other words, the IDL attributes, in essence, reflect the content attributes. Most of the time, IDL attributes will return their values as they are really used. For example, the default type for <input> elements is "text", so if you set input.type="foobar" , the <input> element will be of type text (in the appearance and the behavior) but the "type" content attribute's value will be "foobar". However, the type IDL attribute will return the string "text". IDL attributes are not always strings; for example, input.maxlength is a number (a signed long). When using IDL attributes, you read or set values of the desired type, so input.maxlength is always going to return a number and when you set input.maxlength , it wants a number. If you pass another type, it is automatically converted to a number as specified by the standard JavaScript rules for type conversion. IDL attributes can reflect other types such as unsigned long, URLs, booleans, etc. Unfortunately, there are no clear rules and the way IDL attributes behave in conjunction with their corresponding content attributes depends on the attribute. Most of the time, it will follow the rules laid out in the specification , but sometimes it doesn't. HTML specifications try to make this as developer-friendly as possible, but for various reasons (mostly historical), some attributes behave oddly ( select.size , for example) and you should read the specifications to understand how exactly they behave. Boolean Attributes Some content attributes (e.g., required , readonly , disabled ) are called boolean attributes . If a boolean attribute is present, its value is true , and if it's absent, its value is false . HTML defines restrictions on the allowed values of boolean attributes: If the attribute is present, its value must either be the empty string (equivalently, the attribute may have an unassigned value), or a value that is an ASCII case-insensitive match for the attribute's canonical name, with no leading or trailing whitespace. The following examples are valid ways to mark up a boolean attribute: html <div itemscope>This is valid HTML but invalid XML.</div> <div itemscope=itemscope>This is also valid HTML but invalid XML.</div> <div itemscope="">This is valid HTML and also valid XML.</div> <div itemscope="itemscope"> This is also valid HTML and XML, but perhaps a bit verbose. </div> To be clear, the values "true" and "false" are not allowed on boolean attributes. To represent a false value, the attribute has to be omitted altogether. This restriction clears up some common misunderstandings: With checked="false" for example, the element's checked attribute would be interpreted as true because the attribute is present. Event handler attributes Warning: The use of event handler content attributes is discouraged. The mix of HTML and JavaScript often produces unmaintainable code, and the execution of event handler attributes may also be blocked by content security policies. Warning: While not visible by calling the Function.prototype.toString() method on the handler, event handler attributes will implicitly wrap code inside of 2 with statements, and may produce unexpected results. For example: html <div onclick="console.log(new URL(location))">Bad Example</div> Essentially becomes: js function onclick(event) { with (this.ownerDocument) { with (this) { console.log(new URL(location)); // 'URL' now resolves to document.URL instead of window.URL // TypeError: URL is not a constructor } } } In addition to the attributes listed in the table above, global event handlers — such as onclick — can also be specified as content attributes on all elements. All event handler attributes accept a string. The string will be used to synthesize a JavaScript function like function name(/*args*/) {body} , where name is the attribute's name, and body is the attribute's value. The handler receives the same parameters as its JavaScript event handler counterpart — most handlers receive only one event parameter, while onerror receives five: event , source , lineno , colno , error . This means you can, in general, use the event variable within the attribute. html <div onclick="console.log(event)">Click me!</div> <!-- The synthesized handler has a name; you can reference itself --> <div onclick="console.log(onclick)">Click me!</div> See also HTML elements Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jan 9, 2026 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTML Guides Cheatsheet Comments Constraint validation Content categories Date and time formats Microdata Microformats Quirks and standards modes Responsive images How to Define terms with HTML Use data attributes Use cross-origin images Add a hitmap on top of an image Author fast-loading HTML pages Add JavaScript Reference Elements <a> <abbr> <acronym> Deprecated <address> <area> <article> <aside> <audio> <b> <base> <bdi> <bdo> <big> Deprecated <blockquote> <body> <br> <button> <canvas> <caption> <center> Deprecated <cite> <code> <col> <colgroup> <data> <datalist> <dd> <del> <details> <dfn> <dialog> <dir> Deprecated <div> <dl> <dt> <em> <embed> <fencedframe> Experimental <fieldset> <figcaption> <figure> <font> Deprecated <footer> <form> <frame> Deprecated <frameset> Deprecated <h1> <head> <header> <hgroup> <hr> <html> <i> <iframe> <img> <input> <ins> <kbd> <label> <legend> <li> <link> <main> <map> <mark> <marquee> Deprecated <menu> <meta> <meter> <nav> <nobr> Deprecated <noembed> Deprecated <noframes> Deprecated <noscript> <object> <ol> <optgroup> <option> <output> <p> <param> Deprecated <picture> <plaintext> Deprecated <pre> <progress> <q> <rb> Deprecated <rp> <rt> <rtc> Deprecated <ruby> <s> <samp> <script> <search> <section> <select> <selectedcontent> Experimental <slot> <small> <source> <span> <strike> Deprecated <strong> <style> <sub> <summary> <sup> <table> <tbody> <td> <template> <textarea> <tfoot> <th> <thead> <time> <title> <tr> <track> <tt> Deprecated <u> <ul> <var> <video> <wbr> <xmp> Deprecated Attributes accept autocomplete capture content crossorigin dirname disabled elementtiming fetchpriority for form max maxlength min minlength multiple pattern placeholder readonly rel required size step Global attributes accesskey anchor Experimental Non-standard autocapitalize autocorrect autofocus class contenteditable data-* dir draggable enterkeyhint exportparts hidden id inert inputmode is itemid itemprop itemref itemscope itemtype lang nonce part popover slot spellcheck style tabindex title translate virtualkeyboardpolicy Experimental writingsuggestions Attributes by element <input> type <input type="button"> <input type="checkbox"> <input type="color"> <input type="date"> <input type="datetime-local"> <input type="email"> <input type="file"> <input type="hidden"> <input type="image"> <input type="month"> <input type="number"> <input type="password"> <input type="radio"> <input type="range"> <input type="reset"> <input type="search"> <input type="submit"> <input type="tel"> <input type="text"> <input type="time"> <input type="url"> <input type="week"> <script> type importmap speculationrules Experimental <meta> name color-scheme referrer robots theme-color viewport <meta> http-equiv Attribute values rel keywords rel="alternate stylesheet" rel="compression-dictionary" Experimental rel="dns-prefetch" rel="manifest" rel="me" rel="modulepreload" rel="noopener" rel="noreferrer" rel="preconnect" rel="prefetch" rel="preload" rel="prerender" Non-standard Deprecated Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww.linkedin.com%2FshareArticle%3Fmini%3Dtrue%26url%3Dhttps%253A%252F%252Fdev.to%252Feachampagne%252Fwebsockets-with-socketio-5edp%26title%3DWebsockets%2520with%2520Socket.IO%26summary%3DThis%2520post%2520contains%2520a%2520flashing%2520gif.%2520%2520HTTP%2520requests%2520have%2520taken%2520me%2520pretty%2520far%252C%2520but%2520I%25E2%2580%2599m%2520starting%2520to%2520run...%26source%3DDEV%2520Community | Sign Up | LinkedIn Make the most of your professional life Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Remember me First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/user-preferences#content-area | User Preferences - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences User Preferences Tenant Preferences Preference Evaluation Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Preferences User Preferences Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Preferences User Preferences OpenAI Open in ChatGPT Learn how user preferences work in SuprSend and how to capture them. OpenAI Open in ChatGPT Before you start: Make sure you’ve set up notification categories first. See Manage Categories and Preferences for step-by-step instructions. Preferences let users control which notifications they receive. Instead of an all-or-nothing approach, users can opt out of specific categories, choose preferred channels, and set notification frequency. This granular control reduces the chance that users disable all notifications from your platform. In SuprSend, you can use ready-made UI and APIs to manage multi-tenant preference use cases. This includes letting admins set preferences for internal teams and handle notifications for enterprise customers, where companies, customers, and end users have distinct preferences. How It Works Preferences are evaluated in priority order: User Preference → Tenant Default → Category Default Three Levels of Control Global channel opt-outs, category preferences, and channel opt-outs within categories What are user preferences? Preferences only work with sub-categories: User preferences apply to sub-categories you create, not root-categories (System, Transactional, Promotional). Use sub-category slugs in workflows for preferences to work. Each user has a preference set that controls which notifications they receive. A preference set has three levels of control: channel_preferences — Global channel opt-outs (e.g., opt out of all email) categories — Category-level preferences (opt in/out of all channels of a notification type) opt_out_channels — Opt-in/out of specific channels within a category Example: Copy Ask AI { "channel_preferences" : [ { "channel" : "email" , "is_restricted" : true } ], "categories" : [ { "category" : "invoice-ready" , "preference" : "opt_out" }, { "category" : "payment-reminder" , "preference" : "opt_in" , "opt_out_channels" : [ "slack" ] } ] } In this example: user opted out of email globally, opted out of invoice-ready category completely, and stays opted in to payment-reminder but without Slack. How preferences are determined When a user hasn’t set their own preferences in a category, SuprSend uses defaults in this order: User Preference — Individual user’s explicit choices (highest priority) Tenant Default Preference — Default preferences set by tenant for the category Category Default Preference — Default preferences set at the category level (lowest priority) Preference precedence: User Preference → Tenant Default Preference → Category Default Preference Preference precedence is determined at category level . So, if a user overrides preference for a category but doesn’t touch other categories, defaults continue to apply to the untouched categories. Setting up preference categories Before users can set their preferences, you must first create and configure preference categories. For step-by-step setup instructions, see Manage Categories and Preferences . Default preferences Default preferences determine how users receive notifications when they haven’t set their own preferences. Configure these at the sub-category level when setting up categories. What default preferences control Default preferences control: Channel or Category defaults : Which categories or channels will be turned on/off by default on users’ preference page. Mandatory channels : Which channel or category users cannot opt out of (shown as disabled on preference page) Visibility : Whether a category appears on the preference page Preference types On — Users receive this category's notifications by default Users will receive notifications in this category by default. You can configure Opt-in Channels to specify which channels are included in the default “On” state: All : All available channels are enabled by default Selected Channels only : Only specific channels you select are enabled by default (e.g., Email, Android Push, iOS Push, In-App Inbox, MS Teams, Slack) Off — Users must opt in to get notifications Users will not receive notifications unless they change the preference. Can't Unsubscribe — Users cannot opt out of mandatory channels in this category Prevents users from fully opting out of the category. When selected, you can configure: Mandatory Channels : Channels which can’t be opted out of by the user. Set to “All” or “Selected Channels”. Opt-in Channels : In case of “Selected” Mandatory Channels, you can configure the channels that will be opted in by default. Channels other than mandatory and opt-in will be skipped for sending notification unless user explicitly opts in to them. Even when a category is set to “Can’t Unsubscribe,” users can still control channel-level preferences if your channel-level settings allow it. This configuration gives you fine-grained control over which channels a user is opted into by default, letting you differentiate between must-deliver channels, default-on channels, and optional channels. Capturing user preferences Users can set their preferences through one of the following methods: Hosted preference page Once you publish preference categories, SuprSend automatically generates a dedicated unsubscription webpage for collecting user preferences . Users can set channel-specific preferences from the hosted page. If the link is included in an email, the hosted page will show and save email preferences. Include it in your templates using {{$hosted_preference_url}} . This page is currently hosted on a SuprSend domain, but you can reach out to [email protected] if you’d prefer it hosted on your own domain. Embed in your product You can embed the preference interface directly inside your product using SuprSend’s ready-made UI components. SDKs exist in the languages below. Update your product preference page link on the tenant page and render it in templates using {{$embedded_preference_url}} . Javascript React Angular Embeddable preference page Controlling what categories to show on UI It’s always a good practice to show only the categories that are relevant to the user. There are two ways to achieve this: Hide categories for tenant users In a multi-tenant setup, tenants or admins can control which categories their users see. Setting visible_to_subscriber: false in tenant preferences hides the category from tenant users’ preference pages. Hidden categories won’t send notifications to those users, even if they previously opted in. Filter categories with tags Use tags to show categories based on user roles, departments, or teams. Filter categories in the preference center using the tags query parameter. 1 Setting Preference tags Tags can be added to sections and sub-categories directly from Developers → Notification Categories in the SuprSend Console. When a tag is assigned at the section level, it automatically applies to all categories under that section—so filtering by a section tag also filters its child categories. 2 Filter Categories with Tags You can filter categories using the tags query parameter in the API. This can be a simple tag match (e.g. tags=tag1 ) or a more advanced filter using logical operators. Supported operators: Operator Operand Datatype Description Example exists boolean Returns categories where any tag is set tags={ "exists": true } not string Excludes categories that have the specified tag tags={ "not": "admin" } or array Returns categories that match any of the provided tags tags={ "or": ["sales", "marketing"] } and array Returns categories that match all provided tags tags={ "and": ["sales", "manager"] } You can combine these operators for nested filtering like tags={ "or": [{ "and": ["sales", "manager"] }, { "and": ["marketing", "associate"] }] } . If no tags are provided, the preference center returns all visible categories. For details on how tags work, see Tags . Translating preference categories in user’s locale Upload translation files for your category names and descriptions. See How to manage Category translations for details. Once uploaded, pass a locale parameter (e.g., es , fr , de ) when: Loading the embeddable preference center As a query parameter in the get user preference API . The hosted preference page picks the locale from user’s profile. On hosted preference page, Dynamic content (category names, descriptions) is translated using translation files you upload. Static content (CTA text, labels, buttons, etc.) is translated automatically using SuprSend’s built-in i18n support for commonly used languages. You can see the list of supported languages below. Supported languages Language Code English en Spanish es French fr German de Italian it Portuguese pt Catalan ca Russian ru Dutch nl Polish pl Japanese ja Vietnamese vi Language Code Indonesian id Korean ko Serbian sr Norwegian no Hebrew he Chinese zh Finnish fi Swedish sv Czech cs Lithuanian lt Arabic ar How preferences are evaluated SuprSend evaluates user preferences at send time. For every recipient, the system checks user-level preferences first, then tenant-level overrides, and finally category defaults. For detailed information on the evaluation process, see Preference Evaluation . Other ways to unsubcribe from notifications In addition to the preference center within SuprSend, communication channels provide their own opt-out options, which SuprSend manages internally. Email: Unsubscribe URL header Gmail requires an unsubscribe URL in email headers when sending bulk emails (5,000+ emails/day). Most email providers expect you to add your own unsubscription page or offer a basic all-or-nothing opt-out option. You can add {{$hosted_preference_url}} here to load the SuprSend hosted preference page from the email header. Inbox (In-App): Render preference page inside your Inbox Companies also give users the option to load preference settings inside their in-app Inbox or provide a link to redirect users to the Preference center in their product. Mobile Push: Preference Page in App settings For mobile push notifications, users typically manage their preferences through the app settings. The category you assign in your workflow is also sent as the push “category” (used by Android/iOS to group notifications). If you set preference categories, the system automatically reflects them in the user’s app settings, loading similar preference controls. SMS & Whatsapp: Reply `STOP` Users generally unsubscribe from Short Message Service (SMS) by replying “STOP.” SuprSend automatically marks the SMS channel as inactive in the user’s profile when it receives a STOP reply. For WhatsApp, opt-out behavior depends on the provider; where supported, users can reply STOP and SuprSend will mark the channel inactive. FAQ How do I set up a digest schedule? You can create sub-categories for different digest schedules or set the digest schedule in the user profile and pass a dynamic schedule in the workflow digest node. An option to set the digest schedule directly on your preference page will be available soon. I have a use case where a company has multiple departments/roles, and the admin will set preferences for users in these departments. You can manage this with tenant preferences. In the SuprSend system, each tenant represents an organization, and the administrator sets which categories to send to their internal team using the tenant preference API . What happens to existing user preference view if I change default preference setting? Changing the default preference for a category doesn’t affect users who have already made changes to that category. For categories where users haven’t made any changes, the preferences update according to the new default settings. I have multiple enterprise customers with various product offerings. Customers should only receive notifications for the products they have enabled, and the same should be visible on their preference page. How can I manage this in SuprSend? You can turn off categories for tenants from the tenant page on the SuprSend console. Turning off the preference for a category automatically removes it from the tenant preference APIs and UI view. To further apply this to the tenant’s users, set visible to subscriber to false in the default tenant preferences to hide the category from the tenant’s end users. Why don't I see the 'inbox' channel in my user preferences? The inbox channel preference is behind a feature flag and needs to be enabled for your account. If you don’t see the inbox channel in your user preferences, contact [email protected] to have the feature flag enabled for your workspace. Why do users still receive promotional notifications even after unsubscribing from all categories? Unsubscribing from top-level categories (System, Transactional, Promotional) is not supported . Preferences only work with sub-categories you create. If you’re sending notifications using a top-level category like "promotional" in your workflows, users cannot unsubscribe from those notifications through the preference center, even if they unsubscribe from all visible categories. Solution: Create sub-categories under the Promotional category (e.g., “Marketing”, “Newsletter”, “Product Updates”) and use those sub-category slugs in your workflows instead of the top-level category. This allows users to: See and control preferences for each notification type Opt out of specific sub-categories Have their preferences respected when you send notifications Best practice: Organize notifications into meaningful sub-categories rather than using top-level categories directly. This provides users with granular control and improves their experience. Can I use user preferences in workflow branching to control which notifications are sent? User preferences are not passed in the workflow payload, so you cannot directly access them in branch conditions or other workflow nodes. Workaround: If you need to use preference-based logic in workflows (e.g., to route notifications based on user preferences or combine multiple notification scenarios in a single workflow), you can: Store the same preference data as custom properties in the user profile Use those custom properties in branch conditions to route notifications Example use case: If you want to combine multiple notification scenarios (e.g., “New Comment”, “Reply on my comment”, “I am mentioned”) in a single workflow to avoid duplicate notifications, you can: Store user preferences for each scenario as custom properties (e.g., wants_new_comment_notifications: true , wants_mention_notifications: true ) Use branch conditions to check these properties and route notifications accordingly This allows you to have one workflow that handles all scenarios while respecting user preferences Alternative approach: Create separate workflows for each notification scenario with conditions in the Trigger node. Each workflow can use its own preference category, allowing users to control each scenario independently. How do I let users control both notification on/off and the time they want to be reminded (e.g., medicine reminders)? You can combine preference categories with dynamic digest schedules to achieve this: 1. Set up preference categories: Create a preference category (e.g., “medicine-reminders”) that users can opt in/out of using the preference APIs or preference center UI . 2. Store time preference as user property: When users select their preferred reminder time, store it as a custom property in their user profile. For example: Copy Ask AI user.set({ "medicineReminderTime" : { "frequency" : "daily" , "time" : "09:00" , "tz_selection" : "recipient" } }) 3. Use dynamic schedule in digest node: In your workflow’s digest node, configure it to use a dynamic schedule that references the user property (e.g., ."$recipient".medicineReminderTime ). The digest will only send if the user has opted in to the category, and it will send at their preferred time. Implementation flow: Client side (React Native) : Capture user’s time preference and call your backend API Server side (Supabase Edge Function) : Update both the user’s preference (opt in/out) via SuprSend preference API and store the time preference as a user property Workflow : Use preference category to control on/off, and dynamic schedule to control timing For detailed information, see Dynamic Schedule in the digest documentation. Related documentation Notification Categories - Setting up categories & defaults Manage Categories and Preferences - Complete guide to setting up and managing categories and preferences Tenant Preferences - Managing tenant-level preferences Preference Evaluation - How SuprSend evaluates preferences at runtime Was this page helpful? Yes No Suggest edits Raise issue Previous Tenant Preferences Learn how to manage preferences for your tenants and their users. Next ⌘ I x github linkedin youtube Powered by On this page What are user preferences? How preferences are determined Setting up preference categories Default preferences What default preferences control Preference types Capturing user preferences Hosted preference page Embed in your product Controlling what categories to show on UI Hide categories for tenant users Filter categories with tags Translating preference categories in user’s locale How preferences are evaluated Other ways to unsubcribe from notifications FAQ Related documentation | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Learn_web_development/Getting_started | Getting started modules - Learn web development | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Learn Getting started modules Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Русский 中文 (简体) Getting started modules Welcome to Getting started ! If you are a complete beginner (i.e., you've not installed a code editor or written any code yet), then this is the place to be. The Getting started modules take you through installing the software you need, familiarity with your development environment, taking your first stab at building a simple website, and understanding some of the essential concepts surrounding web development. In this article Prerequisites Modules See also Prerequisites There is no prerequisite knowledge for starting this course. Also note that we don't consider learning these topics as required before moving on to the Core modules , but we believe students will have an easier time if they spend some time on these topics first. Modules Environment setup In the Environment setup module, we show you what tools you need to do simple web development and how to install them properly and help you understand important aspects of your environment such as file systems and the command line. Your first website This module introduces you to the practicalities of web development. You'll gather the assets and write the code to construct and publish a simple webpage. Web standards This module covers the fundamentals of how the web works at a high level — including the model used for communication, the core technologies involved, how those technologies are created, and how a web browser renders and displays websites to a user. Soft skills This module provides recommendations of soft skills you can aim to get better at while learning web development, and which constitute good traits to have when entering the industry. They will help immensely in developing the right attitudes for learning, researching, and collaborating, and increase the chances of getting hired. See also The Frontend Developer Career Path MDN learning partner Scrimba's Frontend Developer Career Path teaches all you need to know to be a competent front-end web developer, with fun interactive lessons and challenges, knowledgeable teachers, and a supportive community. Go from zero to landing your first front-end job! Many of the course components are available as standalone free versions. Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Apr 18, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Learn web development MDN curriculum Getting started modules Environment setup Installing software Browsing the web Code editors Dealing with files Command line Your first website What will it look like? Creating the content Styling the content Adding interactivity Publishing Web standards How the web works The web standards model How browsers load websites Soft skills Research and learning Collaboration and teamwork Workflows and processes Finding a job Core modules Structuring content with HTML Basic HTML syntax Web page metadata Headings and paragraphs Emphasis and importance Lists Test: HTML text basics Advanced text features Test: Advanced HTML text Challenge: Letter markup Structuring documents Creating links Test: Links Challenge: Bird watching site Images Test: Images Video and audio Test: Audio and video Challenge: Splash page Table basics Table accessibility Challenge: Planet data table Forms and buttons Test: Forms and buttons Challenge: Feedback form Debugging HTML Test: HTML tests index Additional tutorials Vector graphics Embedding technologies CSS styling basics What is CSS? CSS getting started Challenge: Biography page Basic selectors Attribute selectors Pseudo-classes and elements Combinators Test: Selectors Box model Test: Box model Handling conflicts Test: Cascade Challenge: Fixing blog styles Values and units Test: Values and units Sizing Test: Sizing Backgrounds and borders Test: Backgrounds and borders Overflow Test: Overflow Challenge: Sizing and decorating Images, media, forms Test: Images and forms Styling tables Challenge: Styling color scheme search Debugging CSS Test: Styling basics tests index Additional tutorials Advanced styling effects Cascade layers Multiple text directions Organizing your CSS CSS text styling Text and font fundamentals Styling lists Styling links Web fonts Challenge: Community school homepage CSS layout Introduction Floats Test: Floats Positioning Test: Positioning Flexbox Test: Flexbox CSS grid layout Test: CSS grid Challenge: Fundamental layout Responsive web design Media queries Test: RWD & media queries Challenge: mobile-first Test: Layout tests index Additional tutorials Multiple-column layout Practical positioning examples Legacy layout methods Supporting older browsers Dynamic scripting with JavaScript What is JavaScript? JavaScript walkthrough Troubleshooting Variables Test: Variables Numbers and operators Test: Math Strings String methods Test: Strings Arrays Test: Arrays Challenge: Story generator Conditionals Test: Conditionals Loops Test: Loops Functions Build your own function Function return values Test: Functions Events Event bubbling Test: Events Objects Test: Objects DOM scripting Challenge: Image gallery Network requests JSON Test: JSON Challenge: House data UI Debugging and error handling Test: JavaScript tests index JavaScript frameworks and libraries Introduction Framework features React getting started React ToDo app React components React events and state React editing, filtering, conditional UI React accessibility React resources Accessibility What is accessibility? Accessibility tools Accessible HTML Test: HTML a11y Accessible CSS and JS Test: CSS/JS a11y WAI-ARIA Test: WAI-ARIA Accessible multimedia Mobile accessibility Challenge: A11y debugging Test: A11y tests index Design for developers Version control Extension modules Advanced JavaScript objects Object prototypes Object-oriented programming Classes in JavaScript Test: Object-oriented JavaScript Object building practice Challenge: Bouncing balls features Test: OOJS tests index Client-side web APIs Introduction Video and audio Drawing graphics Client-side storage Third-party APIs Asynchronous JavaScript Introduction Using promises Implementing promise-based APIs Introducing workers Challenge: Animation sequence Web forms Your first form How to structure a web form Basic native form controls The HTML5 input types Other form controls Styling web forms Advanced form styling Customizable selects UI pseudo-classes Client-side form validation Sending form data Additional tutorials Custom form controls JS form submission Forms in legacy browsers UI methods & controls Understanding client-side tools Overview Package management Sample toolchain Deploying our app Server-side websites First steps Introduction Client-server overview Server-side frameworks Website security Django (Python) Django introduction Dev environment setup 1: Local library tutorial 2: Skeleton website 3: Models 4: Django admin site 5: Home page 6: Generic list and detail views 7: Sessions framework 8: Authentication and permissions 9: Forms 10: Testing 11: Deploying Django security Challenge: Django blog Express (Node.js) Express/Node introduction Dev environment setup 1: Local library tutorial 2: Skeleton website 3: Using databases with Mongoose 4: Routes and controllers 5: Displaying data 6: Working with forms 7: Deploying Additional tutorials Apache .htaccess Server MIME type config Plain Node.js server Web performance The "why" of web performance What is web performance? Perceived performance Measuring performance Multimedia: Images Multimedia: video Performant JavaScript Performant HTML Performant CSS Performance business case Best practices & tips Testing Introduction Testing strategies Common HTML and CSS problems Feature detection Automated testing Automation environment setup Further resources How to solve common problems Common CSS problems Common HTML problems Common JavaScript problems Design and accessibility Tools and setup Web mechanics About Resources for educators Changelog Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/sms-template#design-template | SMS Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors SMS Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors SMS Template OpenAI Open in ChatGPT How to design and publish SMS template. OpenAI Open in ChatGPT Design Template You can design SMS template on SuprSend with a simple form editor tool. You can add variables with Handlebarsjs language. You can check how the message will look in the preview section on the right side. The SMS template has 3 parts: Message type (Transactional, Promotional, Engagement), Header (template headers added in the SMS integration settings), Body (SMS template is added here). Once designed, you can save the SMS template by clicking on “Save” button. When you are ready, you can Publish Draft by providing a name to the version. This will create a version in ‘Pending Approval’ state. Every SMS template goes through an approval process, where the templates are submitted to the registered DLT portal for review, where the SMS is reviewed based on the DLT guidelines and SMS either gets approved or rejected. SuprSend handles the template approval process for you. All you have to do is create a template on SuprSend while following DLT template guidelines, and wait for the approval / rejection of template. Accordingly, the published template version’s state will move to Live or Rejected . Once the version goes Live , you can use the template to send to your users. SMS fields description Field Description Message Type There are 3 types of message - (1) Transactional - Service implicit or Informative messages which are triggered corresponding to a user’s action either done at the time of sending the message or based on past data. All other OTPs other than bank OTPs also fall in this category. e.g.- delivery updates, E-commerce website OTPs etc. (2) Promotional - All the marketing related messages where we have not taken any explicit consent from the user. e.g.- messages sent to promote or sell a product (3) Engagement - Service Explicit or Engagement messages which are triggered to re-engage the users back to platform like promoting new features and offers. e.g.- new feature promotion, discount offer messages to existing customers etc. Header Header should be registered with DLT. Separate headers would be there for all the message types Body SMS template added here should follow DLT template guidelines. Click here to view all DLT guidelines Please note that to send the SMS, you will need to integrate SMS vendor with SuprSend. Please visit the ‘Vendor Integration Guideline’ section to see vendors list and how to integrate them. Vendor Integration Required 📘 Please note that to send the SMS, you will need to integrate SMS vendor with SuprSend. Please visit the ‘Vendor Integration Guideline’ section to see vendors list and how to integrate them. Adding dynamic content in SMS There will always be the case where you would be required to add dynamic content to a template, so as to personalise it for your users. To achieve this, you can add variables in the template, which will be replaced with the dynamic content at the time of sending email. To send actual values to replace variables at the time of communication trigger, use one of our frontend or backend SDKs. Here is a step by step guide on how to add dynamic content in a template: 1 Declaring Variables in the global 'Mock data' button: If you are at this stage, it is assumed that you have declared the variables along with sample values in the global Mock data button. To see how to declare variables before using them in designing templates, refer to this section in the Templates documentation . 2 Using variables in the templates: Once the variables are declared, you can use them while designing template for any channel. We support handlebarsjs to add variables in the template. As a general rule, all the variables have to be entered within double curly brackets: {{variable\_name}} If you have declared the variables and added sample data in the global Mock data button, then they will come as auto-suggestions when you type a curly bracket { . This will remove the chances of error like variable mismatch at the time of template rendering. Note that you will be able to enter a variable name even when you have not declared it inside the Variables button. To manually enter the variable name, follow the handlerbarsjs guide here . Below are some examples of how to enter variables in the template design. For illustration, we are using the same sample variable names that we declared in the Templates section: json Copy Ask AI { "array" : [ { "product_name" : "Aldo Sling Bag" , "product_price" : "3,950.00" }, { "product_name" : "Clarles & Keith Women Slipper, Biege, 38UK" , "product_price" : "2,549.00" }, { "product_name" : "RayBan Sunglasses" , "product_price" : "7,899.00" } ], "event" : { "location" : { "city" : "Bangalore" , "state" : "KA" }, "order_id" : "11200123" , "first_name" : "Nikita" }, "product_page" : "https://www.suprsend.com" } To enter a nested variable, enter in the format {{var1.var2.var3}} . Eg. to refer to city in the example above, you need to enter {{event.location.city}} If you have any space in the variable name, enclose it in square bracket {{event.[first name]}} To refer to an array element, enter in format {{var1.[index].var2}} . Eg. to refer to product_name of the first element of the array array , enter {{array.[0].product_name}} At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user. Please note that the rest of the templates will be sent. Eg. if there is an error in rendering Android Push template, but SMS template is successfully rendered, Android Push notification will not be triggered, but SMS notification will be triggered by SuprSend. Was this page helpful? Yes No Suggest edits Raise issue Previous Whatsapp Template How to design whatsapp template using form editor. Next ⌘ I x github linkedin youtube Powered by On this page Design Template SMS fields description Adding dynamic content in SMS | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators | Expressions and operators - JavaScript | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web JavaScript Reference Expressions and operators Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Expressions and operators This chapter documents all the JavaScript language operators, expressions and keywords. In this article Expressions and operators by category Specifications Browser compatibility See also Expressions and operators by category For an alphabetical listing see the sidebar on the left. Primary expressions Basic keywords and general expressions in JavaScript. These expressions have the highest precedence (higher than operators ). this The this keyword refers to a special property of an execution context. Literals Basic null , boolean, number, and string literals. [] Array initializer/literal syntax. {} Object initializer/literal syntax. function The function keyword defines a function expression. class The class keyword defines a class expression. function* The function* keyword defines a generator function expression. async function The async function defines an async function expression. async function* The async function* keywords define an async generator function expression. /ab+c/i Regular expression literal syntax. `string` Template literal syntax. ( ) Grouping operator. Left-hand-side expressions Left values are the destination of an assignment. Property accessors Member operators provide access to a property or method of an object ( object.property and object["property"] ). ?. The optional chaining operator returns undefined instead of causing an error if a reference is nullish ( null or undefined ). new The new operator creates an instance of a constructor. new.target In constructors, new.target refers to the constructor that was invoked by new . import.meta An object exposing context-specific metadata to a JavaScript module. super The super keyword calls the parent constructor or allows accessing properties of the parent object. import() The import() syntax allows loading a module asynchronously and dynamically into a potentially non-module environment. Increment and decrement Postfix/prefix increment and postfix/prefix decrement operators. A++ Postfix increment operator. A-- Postfix decrement operator. ++A Prefix increment operator. --A Prefix decrement operator. Unary operators A unary operation is an operation with only one operand. delete The delete operator deletes a property from an object. void The void operator evaluates an expression and discards its return value. typeof The typeof operator determines the type of a given object. + The unary plus operator converts its operand to Number type. - The unary negation operator converts its operand to Number type and then negates it. ~ Bitwise NOT operator. ! Logical NOT operator. await Pause and resume an async function and wait for the promise's fulfillment/rejection. Arithmetic operators Arithmetic operators take numerical values (either literals or variables) as their operands and return a single numerical value. ** Exponentiation operator. * Multiplication operator. / Division operator. % Remainder operator. + (Plus) Addition operator. - Subtraction operator. Relational operators A comparison operator compares its operands and returns a boolean value based on whether the comparison is true. < (Less than) Less than operator. > (Greater than) Greater than operator. <= Less than or equal operator. >= Greater than or equal operator. instanceof The instanceof operator determines whether an object is an instance of another object. in The in operator determines whether an object has a given property. Note: => is not an operator, but the notation for Arrow functions . Equality operators The result of evaluating an equality operator is always of type boolean based on whether the comparison is true. == Equality operator. != Inequality operator. === Strict equality operator. !== Strict inequality operator. Bitwise shift operators Operations to shift all bits of the operand. << Bitwise left shift operator. >> Bitwise right shift operator. >>> Bitwise unsigned right shift operator. Binary bitwise operators Bitwise operators treat their operands as a set of 32 bits (zeros and ones) and return standard JavaScript numerical values. & Bitwise AND. | Bitwise OR. ^ Bitwise XOR. Binary logical operators Logical operators implement boolean (logical) values and have short-circuiting behavior. && Logical AND. || Logical OR. ?? Nullish Coalescing Operator. Conditional (ternary) operator (condition ? ifTrue : ifFalse) The conditional operator returns one of two values based on the logical value of the condition. Assignment operators An assignment operator assigns a value to its left operand based on the value of its right operand. = Assignment operator. *= Multiplication assignment. /= Division assignment. %= Remainder assignment. += Addition assignment. -= Subtraction assignment <<= Left shift assignment. >>= Right shift assignment. >>>= Unsigned right shift assignment. &= Bitwise AND assignment. ^= Bitwise XOR assignment. |= Bitwise OR assignment. **= Exponentiation assignment. &&= Logical AND assignment. ||= Logical OR assignment. ??= Nullish coalescing assignment. [a, b] = arr , { a, b } = obj Destructuring allows you to assign the properties of an array or object to variables using syntax that looks similar to array or object literals. Yield operators yield Pause and resume a generator function. yield* Delegate to another generator function or iterable object. Spread syntax ...obj Spread syntax allows an iterable, such as an array or string, to be expanded in places where zero or more arguments (for function calls) or elements (for array literals) are expected. In an object literal, the spread syntax enumerates the properties of an object and adds the key-value pairs to the object being created. Comma operator , The comma operator allows multiple expressions to be evaluated in a single statement and returns the result of the last expression. Specifications Specification ECMAScript® 2026 Language Specification # sec-multiplicative-operators ECMAScript® 2026 Language Specification # sec-unary-plus-operator ECMAScript® 2026 Language Specification # prod-BitwiseORExpression ECMAScript® 2026 Language Specification # prod-PropertyDefinition ECMAScript® 2026 Language Specification # sec-new-operator ECMAScript® 2026 Language Specification # sec-super-keyword ECMAScript® 2026 Language Specification # sec-async-function-definitions ECMAScript® 2026 Language Specification # sec-assignment-operators ECMAScript® 2026 Language Specification # sec-comma-operator ECMAScript® 2026 Language Specification # prod-BitwiseANDExpression ECMAScript® 2026 Language Specification # sec-grouping-operator ECMAScript® 2026 Language Specification # sec-relational-operators ECMAScript® 2026 Language Specification # sec-function-definitions ECMAScript® 2026 Language Specification # sec-import-calls ECMAScript® 2026 Language Specification # prod-ImportMeta ECMAScript® 2026 Language Specification # prod-BitwiseXORExpression ECMAScript® 2026 Language Specification # sec-left-shift-operator ECMAScript® 2026 Language Specification # sec-typeof-operator ECMAScript® 2026 Language Specification # sec-addition-operator-plus ECMAScript® 2026 Language Specification # sec-delete-operator ECMAScript® 2026 Language Specification # sec-exp-operator ECMAScript® 2026 Language Specification # sec-equality-operators ECMAScript® 2026 Language Specification # sec-class-definitions ECMAScript® 2026 Language Specification # sec-subtraction-operator-minus ECMAScript® 2026 Language Specification # sec-object-initializer ECMAScript® 2026 Language Specification # sec-generator-function-definitions ECMAScript® 2026 Language Specification # prod-SpreadElement ECMAScript® 2026 Language Specification # prod-CoalesceExpression ECMAScript® 2026 Language Specification # prod-LogicalANDExpression ECMAScript® 2026 Language Specification # sec-postfix-increment-operator ECMAScript® 2026 Language Specification # sec-postfix-decrement-operator ECMAScript® 2026 Language Specification # sec-destructuring-assignment ECMAScript® 2026 Language Specification # sec-destructuring-binding-patterns ECMAScript® 2026 Language Specification # prod-OptionalExpression ECMAScript® 2026 Language Specification # sec-signed-right-shift-operator ECMAScript® 2026 Language Specification # prod-ArgumentList ECMAScript® 2026 Language Specification # sec-generator-function-definitions-runtime-semantics-evaluation ECMAScript® 2026 Language Specification # sec-bitwise-not-operator ECMAScript® 2026 Language Specification # sec-built-in-function-objects ECMAScript® 2026 Language Specification # prod-YieldExpression ECMAScript® 2026 Language Specification # sec-void-operator ECMAScript® 2026 Language Specification # sec-this-keyword ECMAScript® 2026 Language Specification # sec-null-value ECMAScript® 2026 Language Specification # sec-logical-not-operator ECMAScript® 2026 Language Specification # sec-unary-minus-operator ECMAScript® 2026 Language Specification # sec-async-generator-function-definitions ECMAScript® 2026 Language Specification # sec-unsigned-right-shift-operator ECMAScript® 2026 Language Specification # sec-property-accessors ECMAScript® 2026 Language Specification # prod-LogicalORExpression ECMAScript® 2026 Language Specification # sec-conditional-operator HTML # import-meta-resolve Browser compatibility Enable JavaScript to view this browser compatibility table. See also Operator precedence Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jul 8, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar JavaScript Tutorials and guides JavaScript Guide Introduction Grammar and types Control flow and error handling Loops and iteration Functions Expressions and operators Numbers and strings Representing dates & times Regular expressions Indexed collections Keyed collections Working with objects Using classes Using promises JavaScript typed arrays Iterators and generators Resource management Internationalization JavaScript modules Intermediate Language overview JavaScript data structures Equality comparisons and sameness Enumerability and ownership of properties Closures Advanced Inheritance and the prototype chain Meta programming Memory Management References Built-in objects AggregateError Array ArrayBuffer AsyncDisposableStack AsyncFunction AsyncGenerator AsyncGeneratorFunction AsyncIterator Atomics BigInt BigInt64Array BigUint64Array Boolean DataView Date decodeURI() decodeURIComponent() DisposableStack encodeURI() encodeURIComponent() Error escape() Deprecated eval() EvalError FinalizationRegistry Float16Array Float32Array Float64Array Function Generator GeneratorFunction globalThis Infinity Int8Array Int16Array Int32Array InternalError Non-standard Intl isFinite() isNaN() Iterator JSON Map Math NaN Number Object parseFloat() parseInt() Promise Proxy RangeError ReferenceError Reflect RegExp Set SharedArrayBuffer String SuppressedError Symbol SyntaxError Temporal TypedArray TypeError Uint8Array Uint8ClampedArray Uint16Array Uint32Array undefined unescape() Deprecated URIError WeakMap WeakRef WeakSet Expressions & operators Addition (+) Addition assignment (+=) Assignment (=) async function expression async function* expression await Bitwise AND (&) Bitwise AND assignment (&=) Bitwise NOT (~) Bitwise OR (|) Bitwise OR assignment (|=) Bitwise XOR (^) Bitwise XOR assignment (^=) class expression Comma operator (,) Conditional (ternary) operator Decrement (--) delete Destructuring Division (/) Division assignment (/=) Equality (==) Exponentiation (**) Exponentiation assignment (**=) function expression function* expression Greater than (>) Greater than or equal (>=) Grouping operator ( ) import.meta import.meta.resolve() import() in Increment (++) Inequality (!=) instanceof Left shift (<<) Left shift assignment (<<=) Less than (<) Less than or equal (<=) Logical AND (&&) Logical AND assignment (&&=) Logical NOT (!) Logical OR (||) Logical OR assignment (||=) Multiplication (*) Multiplication assignment (*=) new new.target null Nullish coalescing assignment (??=) Nullish coalescing operator (??) Object initializer Operator precedence Optional chaining (?.) Property accessors Remainder (%) Remainder assignment (%=) Right shift (>>) Right shift assignment (>>=) Spread syntax (...) Strict equality (===) Strict inequality (!==) Subtraction (-) Subtraction assignment (-=) super this typeof Unary negation (-) Unary plus (+) Unsigned right shift (>>>) Unsigned right shift assignment (>>>=) void operator yield yield* Statements & declarations async function async function* await using Block statement break class const continue debugger do...while Empty statement export Expression statement for for await...of for...in for...of function function* if...else import Import attributes Labeled statement let return switch throw try...catch using var while with Deprecated Functions Arrow function expressions Default parameters get Method definitions Rest parameters set The arguments object [Symbol.iterator]() callee Deprecated length Classes constructor extends Private elements Public class fields static Static initialization blocks Regular expressions Backreference: \1, \2 Capturing group: (...) Character class escape: \d, \D, \w, \W, \s, \S Character class: [...], [^...] Character escape: \n, \u{...} Disjunction: | Input boundary assertion: ^, $ Literal character: a, b Lookahead assertion: (?=...), (?!...) Lookbehind assertion: (?<=...), (?<!...) Modifier: (?ims-ims:...) Named backreference: \k<name> Named capturing group: (?<name>...) Non-capturing group: (?:...) Quantifier: *, +, ?, {n}, {n,}, {n,m} Unicode character class escape: \p{...}, \P{...} Wildcard: . Word boundary assertion: \b, \B Errors AggregateError: No Promise in Promise.any was resolved Error: Permission denied to access property "x" InternalError: too much recursion RangeError: argument is not a valid code point RangeError: BigInt division by zero RangeError: BigInt negative exponent RangeError: form must be one of 'NFC', 'NFD', 'NFKC', or 'NFKD' RangeError: invalid array length RangeError: invalid date RangeError: precision is out of range RangeError: radix must be an integer RangeError: repeat count must be less than infinity RangeError: repeat count must be non-negative RangeError: x can't be converted to BigInt because it isn't an integer ReferenceError: "x" is not defined ReferenceError: assignment to undeclared variable "x" ReferenceError: can't access lexical declaration 'X' before initialization ReferenceError: must call super constructor before using 'this' in derived class constructor ReferenceError: super() called twice in derived class constructor SyntaxError: 'arguments'/'eval' can't be defined or assigned to in strict mode code SyntaxError: "0"-prefixed octal literals are deprecated SyntaxError: "use strict" not allowed in function with non-simple parameters SyntaxError: "x" is a reserved identifier SyntaxError: \ at end of pattern SyntaxError: a declaration in the head of a for-of loop can't have an initializer SyntaxError: applying the 'delete' operator to an unqualified name is deprecated SyntaxError: arguments is not valid in fields SyntaxError: await is only valid in async functions, async generators and modules SyntaxError: await/yield expression can't be used in parameter SyntaxError: cannot use `??` unparenthesized within `||` and `&&` expressions SyntaxError: character class escape cannot be used in class range in regular expression SyntaxError: continue must be inside loop SyntaxError: duplicate capture group name in regular expression SyntaxError: duplicate formal argument x SyntaxError: for-in loop head declarations may not have initializers SyntaxError: function statement requires a name SyntaxError: functions cannot be labelled SyntaxError: getter and setter for private name #x should either be both static or non-static SyntaxError: getter functions must have no arguments SyntaxError: identifier starts immediately after numeric literal SyntaxError: illegal character SyntaxError: import declarations may only appear at top level of a module SyntaxError: incomplete quantifier in regular expression SyntaxError: invalid assignment left-hand side SyntaxError: invalid BigInt syntax SyntaxError: invalid capture group name in regular expression SyntaxError: invalid character in class in regular expression SyntaxError: invalid class set operation in regular expression SyntaxError: invalid decimal escape in regular expression SyntaxError: invalid identity escape in regular expression SyntaxError: invalid named capture reference in regular expression SyntaxError: invalid property name in regular expression SyntaxError: invalid range in character class SyntaxError: invalid regexp group SyntaxError: invalid regular expression flag "x" SyntaxError: invalid unicode escape in regular expression SyntaxError: JSON.parse: bad parsing SyntaxError: label not found SyntaxError: missing : after property id SyntaxError: missing ) after argument list SyntaxError: missing ) after condition SyntaxError: missing ] after element list SyntaxError: missing } after function body SyntaxError: missing } after property list SyntaxError: missing = in const declaration SyntaxError: missing formal parameter SyntaxError: missing name after . operator SyntaxError: missing variable name SyntaxError: negated character class with strings in regular expression SyntaxError: new keyword cannot be used with an optional chain SyntaxError: nothing to repeat SyntaxError: numbers out of order in {} quantifier. SyntaxError: octal escape sequences can't be used in untagged template literals or in strict mode code SyntaxError: parameter after rest parameter SyntaxError: private fields can't be deleted SyntaxError: property name __proto__ appears more than once in object literal SyntaxError: raw bracket is not allowed in regular expression with unicode flag SyntaxError: redeclaration of formal parameter "x" SyntaxError: reference to undeclared private field or method #x SyntaxError: rest parameter may not have a default SyntaxError: return not in function SyntaxError: setter functions must have one argument SyntaxError: string literal contains an unescaped line break SyntaxError: super() is only valid in derived class constructors SyntaxError: tagged template cannot be used with optional chain SyntaxError: Unexpected '#' used outside of class body SyntaxError: Unexpected token SyntaxError: unlabeled break must be inside loop or switch SyntaxError: unparenthesized unary expression can't appear on the left-hand side of '**' SyntaxError: use of super property/member accesses only valid within methods or eval code within methods SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed TypeError: 'x' is not iterable TypeError: "x" is (not) "y" TypeError: "x" is not a constructor TypeError: "x" is not a function TypeError: "x" is not a non-null object TypeError: "x" is read-only TypeError: already executing generator TypeError: BigInt value can't be serialized in JSON TypeError: calling a builtin X constructor without new is forbidden TypeError: can't access/set private field or method: object is not the right class TypeError: can't assign to property "x" on "y": not an object TypeError: can't convert BigInt to number TypeError: can't convert x to BigInt TypeError: can't define property "x": "obj" is not extensible TypeError: can't delete non-configurable array element TypeError: can't redefine non-configurable property "x" TypeError: can't set prototype of this object TypeError: can't set prototype: it would cause a prototype chain cycle TypeError: cannot use 'in' operator to search for 'x' in 'y' TypeError: class constructors must be invoked with 'new' TypeError: cyclic object value TypeError: derived class constructor returned invalid value x TypeError: getting private setter-only property TypeError: Initializing an object twice is an error with private fields/methods TypeError: invalid 'instanceof' operand 'x' TypeError: invalid Array.prototype.sort argument TypeError: invalid assignment to const "x" TypeError: Iterator/AsyncIterator constructor can't be used directly TypeError: matchAll/replaceAll must be called with a global RegExp TypeError: More arguments needed TypeError: null/undefined has no properties TypeError: property "x" is non-configurable and can't be deleted TypeError: Reduce of empty array with no initial value TypeError: setting getter-only property "x" TypeError: WeakSet key/WeakMap value 'x' must be an object or an unregistered symbol TypeError: X.prototype.y called on incompatible type URIError: malformed URI sequence Warning: -file- is being assigned a //# sourceMappingURL, but already has one Warning: unreachable code after return statement Misc JavaScript technologies overview Execution model Lexical grammar Iteration protocols Strict mode Template literals Trailing commas Deprecated features Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Colors/Applying_color | Applying color to HTML elements using CSS - CSS | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web CSS Guides Colors Applying color Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Français 日本語 Português (do Brasil) Русский 中文 (简体) Applying color to HTML elements using CSS With CSS , there are lots of ways to add color to your HTML elements to create the look you want. This guide is a primer introducing how CSS can be used to apply colors to HTML elements. This guide includes lists of the CSS properties that set color in their values and how to use colors both in stylesheets and in other ways . Note: It is important to use colors wisely . Always select appropriate colors, ensuring the contrast between text and the background is sufficient to ensure legibility, and always keep the needs of people with differing visual capabilities in mind. To learn more about CSS colors as a data type, see the CSS <color> data type reference and the CSS color values guide . In this article Properties that can have color Specifying colors as values in stylesheets Other ways to use color See also Properties that can have color At the element level, everything in HTML can have color applied to it. Let's look at the different items rendered on the page — such as text, borders, etc. We'll provide lists of the CSS properties that apply color to each. At a fundamental level, the color property defines the foreground color of an HTML element's content and the background-color property defines the element's background color. These can be used on just about any element. Text Whenever an element is rendered, these properties are used to determine the color of the text, its background, and any decorations on the text. color The color to use when drawing the text and any text decorations (such as the addition of under- or overlines, strike-through lines, and so forth. background-color The text's background color. text-shadow Configures a shadow effect to apply to text. Among the options for the shadow is the shadow's base color (which is then blurred and blended with the background based on the other parameters). See Text drop shadows to learn more. text-decoration-color The default text decorations (such as underlines, strikethroughs, etc.) color is currentColor . This keyword represents the current value of the color property. However, you can override that value and use a different color for them with the text-decoration-color property. text-emphasis-color The color to use when rendering emphasis symbols adjacent to each character in the text. This is used primarily when drawing text for East Asian languages. caret-color The color to use when drawing the caret (sometimes referred to as the text input cursor) within the element. This is only useful in elements that are editable, such as <input> and <textarea> or elements whose HTML contenteditable attribute is set to true . Boxes Every element is a box with some sort of content, and has a background and a border in addition to whatever contents the box may have. Borders See the Borders section for a list of the CSS properties you can use to set the colors of a box's borders. background-color The background color to use in areas of the element that have no foreground content. box-shadow Configures inset shadow and drop shadow effects on the box. Among the options for each shadow is the shadow's base color (which is then blurred and blended with any background based on the other parameters). column-rule-color The color to use when drawing the line separating columns of text when using CSS multi-column layout . outline-color The color to use when drawing an outline around the outside of the element. This outline is different from the border in that it doesn't get space set aside for it in the document. Outlines do not participate in the box model , overlapping other content. Outlines are generally used as focus indicators, indicating which element currently has focus and will receive keyboard input events. Borders Any element can have a border drawn around it. A basic element border is a line drawn around the edges of the element's content. See The box model to learn about the relationship between elements and their borders, and the article Styling borders using CSS to learn more about applying styles to borders. You can use the border shorthand property, which lets you configure everything about the border in one shot (including non-color features of borders, such as its width , style (solid, dashed, etc.), and so forth. border-color shorthand Specifies a single color to use for every side of the element's border. border-left-color , border-right-color , border-top-color , and border-bottom-color Lets you set the color of the corresponding side of the element's border. border-block-start-color and border-block-end-color With these, you can set the color used to draw the borders which are closest to the start and end of the block the border surrounds. In a left-to-right writing mode (such as the way English is written), the block start border is the top edge and the block end is the bottom. This differs from the inline start and end, which are the left and right edges (corresponding to where each line of text in the box begins and ends). border-inline-start-color and border-inline-end-color These let you color the edges of the border closest to the beginning and the end of the start of lines of text within the box. Which side this is will vary depending on the writing-mode , direction , and text-orientation properties, which are typically (but not always) used to adjust text directionality based on the language being displayed. For example, if the box's text is being rendered right-to-left, then the border-inline-start-color is applied to the right side of the border. Specifying colors as values in stylesheets Now that you know which CSS properties let you apply color to elements , you can start adding colors to your websites. Let's look at some examples of using color within a stylesheet . In this example, we use several previously mentioned properties, with the concept of applying colors in CSS being the same no matter the property. Let's look at the result first, before going on to look at the code we need to create it: HTML The HTML responsible for creating the above example is shown here: html <div class="wrapper"> <div class="boxLeft"> <p>This is the first box.</p> </div> <div class="boxRight"> <p>This is the second box.</p> </div> </div> Here we have a wrapper <div> containing two child <div> s, each with a single child paragraph ( <p> ). Each content <div> is given a different look and feel. CSS Let's look at the CSS that creates the above result a piece at a time. Note: We are using multiple different CSS color value types in this example to demonstrate their use. This is not recommended for production code. When writing CSS, use the most intuitive value type for you and your team. css .wrapper { height: 110px; padding: 10px; display: flex; gap: 10px; text-align: center; font: 28px "Marker Felt", "Zapfino", cursive; border: 6px solid mediumturquoise; } div { flex: 1; } The .wrapper class is used to assign styles to the <div> that encloses all of our other content. This establishes the height of the container using height , allowing the width of this block-level element to default to 100% of its parent. Setting the display to flex and adding a 10px gap creates a flex container to lay out the children side by side with a gap between all the container's children. We use flex to let the flex children grow to fill the container; it doesn't effect the flex container itself. Of more interest to our discussion here is the use of the border property to establish a border around the outside edge of the element. This border is a solid line, 6 pixels wide, in the named color mediumturquoise . Within our wrapper, we have a left box and a right box. css .boxLeft { background-color: rgb(245 130 130); outline: 2px solid darkred; } The .boxLeft class, used to style the box on the left, sets up the color of the background and the outline: The box's background color is set by changing the value of the CSS background-color property to rgb(245 130 130) , using the rgb() functional notation. An outline is defined for the box. Unlike the more commonly used border , outline doesn't affect layout at all; it draws over the top of whatever may happen to be outside the element's box instead of making room as border does. This outline is a solid, dark red line that's two pixels thick. Note the use of the darkred keyword when specifying the color. Notice that we're not explicitly setting the text color. That means the value of color will be inherited from the nearest containing element that defines it. By default, that's black. css .boxRight { background-color: hwb(270deg 63% 13%); outline: 4px dashed #6e1478; color: hsl(0deg 95% 95%); text-decoration-line: underline; text-decoration-style: wavy; text-decoration-color: #8f8; text-decoration: underline wavy #8f8; text-shadow: 2px 2px 3px black; } Note: We included the text-decoration-* styles separately because Safari doesn't support text-decoration as a shorthand property. Finally, the .boxRight class sets several styles on the box that's drawn to the right. Then the following colors are established (using five different ways of declaring color values ): The background-color is set using hwb() functional notation — hwb(270deg 63% 13%) . This is a medium purple color. The box's outline is used to specify that the box should be enclosed in a four-pixel thick dashed line whose color is a somewhat deeper purple using the six-digit <hex-color> #6e1478 . The foreground (text) color is specified by setting the color property using hsl() functional notation — hsl(0deg 95% 95%) . This is a very light pinkish color. We add a green wavy line under the text with the text-decoration shorthand, along with the longhand component for browser compatibility. We used the 3-digit <hex-color> #8f8 , which is the equivalent of #88ff88 . Finally, a bit of a shadow is added to the text using text-shadow . Its color parameter is set to black , a <named-color> value. We used five different color syntaxes to demonstrate what is possible. In the real world, you and your team will preferably pick a preferred color notation, with everyone working on a code base using the same color syntax. Other ways to use color CSS isn't the only web technology that supports color. Other examples include: The HTML Canvas API Lets you draw 2D bitmapped graphics in a <canvas> element. See our Canvas tutorial to learn more. SVG (Scalable Vector Graphics) Lets you create images using commands that draw specific shapes, patterns, and lines. SVG commands are formatted as XML, and can be embedded directly into a web page or placed in the page using the <img> element, just like any other type of image. WebGL The Web Graphics Library is an OpenGL ES-based API for drawing high-performance 2D and 3D graphics on the Web. See our WebGL tutorial to find out more. Also see WebGPU , a successor to WebGL for modern GPUs. Note: A few now obsolete HTML attributes accepted colors as values, such as bgcolor and vlink . These attributes only accepted <named-color> and three- or six-digit <hex-color> values. See also <color> data type CSS color values guide Using color wisely CSS color module Drawing graphics Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 16, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar CSS Guides Modules Anchor positioning Animations Backgrounds and borders Basic user interface Borders and box decorations Box alignment Box model Box sizing Cascading and inheritance Color adjustment Colors Compositing and blending Conditional rules Containment Counter styles CSSOM view Custom functions and mixins Custom highlight API Custom properties for cascading variables Display Easing functions Environment variables Filter effects Flexible box layout Font loading Fonts Fragmentation Generated content Grid layout Images Inline layout Lists and counters Logical properties and values Masking Media queries Motion path Multi-column layout Namespaces Nesting Overflow Overscroll behavior Paged media Positioned layout Properties and values API Pseudo-elements Round display Ruby layout Scoping Scroll anchoring Scroll snap Scroll-driven animations Scrollbars styling Selectors Shadow parts Shapes Syntax Table Text Text decoration Transforms Transitions Values and units View transitions Viewport Writing modes Anchor positioning Using anchor positioning Handling overflow Animations Animatable properties Using animations Backgrounds and borders Using multiple backgrounds Resizing background images Scaling SVG backgrounds Box alignment Overview In block layout In flexbox In grid layout In multi-column layout Box model Introduction Margin collapsing Box sizing Aspect ratios Cascade Introduction Inheritance Specificity Property value processing Shorthand properties Cascading variables Using custom properties Colors Applying color Color values Using relative colors Using color wisely Accessibility: Colors and luminance Accessibility: Color contrast Columns Basic concepts Styling columns Using multi-column layouts Spanning and balancing columns Handling overflow Handling content breaks Conditional rules Using feature queries Using container scroll-state queries Containment Container queries Using containment Using container size and style queries CSSOM view Coordinate systems (API) Viewport concepts Custom functions and mixins Using CSS custom functions Display Block and inline layout Flow layout Flow layout and overflow Flow layout and writing modes In flow and out of flow Layout and the containing block Formatting contexts Block formatting context Inline formatting context Using multi-keyword syntax Visual formatting model Environment variables Using environment variables Filter effects Using filter effects Flexbox Basic concepts Flexbox and other layouts Aligning flex items Ordering flex items Controlling flex item ratios Wrapping flex items Typical use cases Fonts OpenType features Variable fonts WOFF Grid Basic concepts Grid and other layouts Using line-based placement Grid template areas Using named grid lines Using auto-placement Aligning items Logical values and writing modes Grid layout and accessibility Common grid layouts Subgrid Masonry layout Experimental Images Using gradients Using object-view-box Styling replaced elements Implementing image sprites Lists and counters Using counters Indenting lists Logical properties Basic concepts For floating and positioning For margins, borders, and padding For sizing Masking Introduction Clipping Multiple masks Mask properties Media queries Using media queries For accessibility Testing Printing Nesting style rules Nesting at-rules Nesting and specificity Using nesting Overflow Creating carousels Positioning Stacking context Example 1 Example 2 Example 3 Stacking floating elements Understanding z-index Using z-index Stacking without z-index Scroll anchoring Overview Scroll-driven animations Scroll-driven animation timelines Scroll snap Basic concepts Using scroll snap events Selectors Selectors and combinators Selector structure Privacy and :visited Using :target Shapes Overview Box-value shapes Image-based shapes Using shape-outside Syntax Introduction Comments At-rules Error handling Text Wrapping and breaking text Handling whitespace Text decoration Text shadows Transforms Using transforms Transitions Using transitions Values and units Value definition syntax Numeric data types Textual data types Using math functions Using typed arithmetic Writing modes Introduction Vertical form controls How to Layout cookbook Media objects Column layouts Center an element Sticky footers Split navigation Breadcrumb navigation List group with badges Pagination Card Grid wrapper Contribute a recipe Cookbook template Tools Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator Reference Properties -moz-* -moz-float-edge Non-standard Deprecated -moz-force-broken-image-icon Non-standard Deprecated -moz-orient Non-standard -moz-user-focus Non-standard Deprecated -moz-user-input Non-standard Deprecated -webkit-* -webkit-border-before Non-standard -webkit-box-reflect Non-standard -webkit-mask-box-image Non-standard -webkit-mask-composite Non-standard -webkit-mask-position-x Non-standard -webkit-mask-position-y Non-standard -webkit-mask-repeat-x Non-standard -webkit-mask-repeat-y Non-standard -webkit-tap-highlight-color Non-standard -webkit-text-fill-color -webkit-text-security Non-standard -webkit-text-stroke -webkit-text-stroke-color -webkit-text-stroke-width -webkit-touch-callout Non-standard Custom properties (--*): CSS variables accent-color align-* align-content align-items align-self alignment-baseline all anchor-name anchor-scope animation-* animation animation-composition animation-delay animation-direction animation-duration animation-fill-mode animation-iteration-count animation-name animation-play-state animation-range animation-range-end animation-range-start animation-timeline animation-timing-function appearance aspect-ratio backdrop-filter backface-visibility background-* background background-attachment background-blend-mode background-clip background-color background-image background-origin background-position background-position-x background-position-y background-repeat background-size baseline-source block-size border-* border border-block border-block-color border-block-end border-block-end-color border-block-end-style border-block-end-width border-block-start border-block-start-color border-block-start-style border-block-start-width border-block-style border-block-width border-bottom border-bottom-color border-bottom-left-radius border-bottom-right-radius border-bottom-style border-bottom-width border-collapse border-color border-end-end-radius border-end-start-radius border-image border-image-outset border-image-repeat border-image-slice border-image-source border-image-width border-inline border-inline-color border-inline-end border-inline-end-color border-inline-end-style border-inline-end-width border-inline-start border-inline-start-color border-inline-start-style border-inline-start-width border-inline-style border-inline-width border-left border-left-color border-left-style border-left-width border-radius border-right border-right-color border-right-style border-right-width border-spacing border-start-end-radius border-start-start-radius border-style border-top border-top-color border-top-left-radius border-top-right-radius border-top-style border-top-width border-width bottom box-* box-align Non-standard Deprecated box-decoration-break box-direction Non-standard Deprecated box-flex Non-standard Deprecated box-flex-group Non-standard Deprecated box-lines Non-standard Deprecated box-ordinal-group Non-standard Deprecated box-orient Non-standard Deprecated box-pack Non-standard Deprecated box-shadow box-sizing break-* break-after break-before break-inside caption-side caret-* caret Experimental caret-animation Experimental caret-color caret-shape Experimental clear clip-* clip Deprecated clip-path clip-rule color-* color color-interpolation color-interpolation-filters color-scheme column-* column-count column-fill column-gap column-rule column-rule-color column-rule-style column-rule-width column-span column-width columns contain-* contain contain-intrinsic-block-size contain-intrinsic-height contain-intrinsic-inline-size contain-intrinsic-size contain-intrinsic-width container-* container container-name container-type content content-visibility corner-* corner-block-end-shape Experimental corner-block-start-shape Experimental corner-bottom-left-shape Experimental corner-bottom-right-shape Experimental corner-bottom-shape Experimental corner-end-end-shape Experimental corner-end-start-shape Experimental corner-inline-end-shape Experimental corner-inline-start-shape Experimental corner-left-shape Experimental corner-right-shape Experimental corner-shape Experimental corner-start-end-shape Experimental corner-start-start-shape Experimental corner-top-left-shape Experimental corner-top-right-shape Experimental corner-top-shape Experimental counter-* counter-increment counter-reset counter-set cursor cx cy d direction display dominant-baseline dynamic-range-limit empty-cells field-sizing fill-* fill fill-opacity fill-rule filter flex-* flex flex-basis flex-direction flex-flow flex-grow flex-shrink flex-wrap float flood-color flood-opacity font-* font font-family font-feature-settings font-kerning font-language-override font-optical-sizing font-palette font-size font-size-adjust font-smooth Non-standard font-stretch Deprecated font-style font-synthesis font-synthesis-position Experimental font-synthesis-small-caps font-synthesis-style font-synthesis-weight font-variant font-variant-alternates font-variant-caps font-variant-east-asian font-variant-emoji font-variant-ligatures font-variant-numeric font-variant-position font-variation-settings font-weight forced-color-adjust gap grid-* grid grid-area grid-auto-columns grid-auto-flow grid-auto-rows grid-column grid-column-end grid-column-start grid-row grid-row-end grid-row-start grid-template grid-template-areas grid-template-columns grid-template-rows hanging-punctuation height hyphenate-character hyphenate-limit-chars hyphens image-* image-orientation image-rendering image-resolution Experimental initial-letter inline-size inset-* inset inset-block inset-block-end inset-block-start inset-inline inset-inline-end inset-inline-start interactivity Experimental interest-* interest-delay Experimental interest-delay-end Experimental interest-delay-start Experimental interpolate-size Experimental isolation justify-* justify-content justify-items justify-self left letter-spacing lighting-color line-* line-break line-clamp line-height line-height-step Experimental list-* list-style list-style-image list-style-position list-style-type margin-* margin margin-block margin-block-end margin-block-start margin-bottom margin-inline margin-inline-end margin-inline-start margin-left margin-right margin-top margin-trim Experimental marker-* marker marker-end marker-mid marker-start mask-* mask mask-border mask-border-mode mask-border-outset mask-border-repeat mask-border-slice mask-border-source mask-border-width mask-clip mask-composite mask-image mask-mode mask-origin mask-position mask-repeat mask-size mask-type math-* math-depth math-shift math-style max-* max-block-size max-height max-inline-size max-width min-* min-block-size min-height min-inline-size min-width mix-blend-mode object-* object-fit object-position object-view-box Experimental offset-* offset offset-anchor offset-distance offset-path offset-position offset-rotate opacity order orphans outline-* outline outline-color outline-offset outline-style outline-width overflow-* overflow overflow-anchor overflow-block overflow-clip-margin overflow-inline overflow-wrap overflow-x overflow-y overlay Experimental overscroll-* overscroll-behavior overscroll-behavior-block overscroll-behavior-inline overscroll-behavior-x overscroll-behavior-y padding-* padding padding-block padding-block-end padding-block-start padding-bottom padding-inline padding-inline-end padding-inline-start padding-left padding-right padding-top page-* page page-break-after Deprecated page-break-before Deprecated page-break-inside Deprecated paint-order perspective perspective-origin place-* place-content place-items place-self pointer-events position-* position position-anchor position-area position-try position-try-fallbacks position-try-order position-visibility print-color-adjust quotes r reading-flow Experimental reading-order Experimental resize right rotate row-gap ruby-* ruby-align ruby-overhang ruby-position rx ry scale scroll-* scroll-behavior scroll-margin scroll-margin-block scroll-margin-block-end scroll-margin-block-start scroll-margin-bottom scroll-margin-inline scroll-margin-inline-end scroll-margin-inline-start scroll-margin-left scroll-margin-right scroll-margin-top scroll-marker-group Experimental scroll-padding scroll-padding-block scroll-padding-block-end scroll-padding-block-start scroll-padding-bottom scroll-padding-inline scroll-padding-inline-end scroll-padding-inline-start scroll-padding-left scroll-padding-right scroll-padding-top scroll-snap-align scroll-snap-stop scroll-snap-type scroll-target-group Experimental scroll-timeline scroll-timeline-axis scroll-timeline-name scrollbar-* scrollbar-color scrollbar-gutter scrollbar-width shape-* shape-image-threshold shape-margin shape-outside shape-rendering speak-as Experimental stop-color stop-opacity stroke-* stroke stroke-dasharray stroke-dashoffset stroke-linecap stroke-linejoin stroke-miterlimit stroke-opacity stroke-width tab-size table-layout text-* text-align text-align-last text-anchor text-autospace text-box text-box-edge text-box-trim text-combine-upright text-decoration text-decoration-color text-decoration-inset Experimental text-decoration-line text-decoration-skip Experimental text-decoration-skip-ink text-decoration-style text-decoration-thickness text-emphasis text-emphasis-color text-emphasis-position text-emphasis-style text-indent text-justify text-orientation text-overflow text-rendering text-shadow text-size-adjust Experimental text-spacing-trim Experimental text-transform text-underline-offset text-underline-position text-wrap text-wrap-mode text-wrap-style timeline-scope top touch-action transform-* transform transform-box transform-origin transform-style transition-* transition transition-behavior transition-delay transition-duration transition-property transition-timing-function translate unicode-bidi user-modify Non-standard Deprecated user-select vector-effect vertical-align view-* view-timeline view-timeline-axis view-timeline-inset view-timeline-name view-transition-class view-transition-name visibility white-space white-space-collapse widows width will-change word-break word-spacing writing-mode x y z-index zoom Selectors & nesting selector Attribute selectors Class selectors ID selectors Keyframe selectors Namespace separator Selector list Type selectors Universal selectors Combinators Child combinator Column combinator Experimental Descendant combinator Next-sibling combinator Subsequent-sibling combinator Pseudo-classes :-moz-* :-moz-broken Non-standard Deprecated :-moz-drag-over Non-standard :-moz-first-node Experimental Non-standard :-moz-handler-blocked Non-standard :-moz-handler-crashed Non-standard :-moz-handler-disabled Non-standard :-moz-last-node Experimental Non-standard :-moz-loading Non-standard :-moz-locale-dir(ltr) Non-standard :-moz-locale-dir(rtl) Non-standard :-moz-only-whitespace Non-standard :-moz-submit-invalid Non-standard :-moz-suppressed Non-standard :-moz-user-disabled Non-standard :-moz-window-inactive Non-standard :active-* :active :active-view-transition :active-view-transition-type() :any-link :autofill :blank Experimental :buffering :checked :current Experimental :default :defined :dir() :disabled :empty :enabled :first-* :first :first-child :first-of-type :focus-* :focus :focus-visible :focus-within :fullscreen :future :has-slotted :has() :heading Experimental :heading() Experimental :host :host-context() Deprecated :host() :hover :in-range :indeterminate :interest-source Experimental :interest-target Experimental :invalid :is() :lang() :last-child :last-of-type :left :link :local-link Experimental :modal :muted :not() :nth-* :nth-child() :nth-last-child() :nth-last-of-type() :nth-of-type() :only-child :only-of-type :open :optional :out-of-range :past :paused :picture-in-picture :placeholder-shown :playing :popover-open :read-only :read-write :required :right :root :scope :seeking :stalled :state() :target-* :target :target-after Experimental :target-before Experimental :target-current Experimental :user-invalid :user-valid :valid :visited :volume-locked :where() Pseudo-elements ::-moz-* ::-moz-color-swatch Non-standard ::-moz-focus-inner Non-standard Deprecated ::-moz-list-bullet Experimental Non-standard ::-moz-list-number Experimental Non-standard ::-moz-meter-bar Non-standard ::-moz-progress-bar Experimental Non-standard ::-moz-range-progress Non-standard ::-moz-range-thumb Non-standard ::-moz-range-track Non-standard ::-webkit-* ::-webkit-inner-spin-button Non-standard ::-webkit-meter-bar Non-standard Deprecated ::-webkit-meter-even-less-good-value Non-standard ::-webkit-meter-inner-element Non-standard ::-webkit-meter-optimum-value Non-standard ::-webkit-meter-suboptimum-value Non-standard ::-webkit-progress-bar Non-standard ::-webkit-progress-inner-element Non-standard ::-webkit-progress-value Non-standard ::-webkit-scrollbar Non-standard ::-webkit-search-cancel-button Non-standard ::-webkit-search-results-button Non-standard ::-webkit-slider-runnable-track Non-standard ::-webkit-slider-thumb Non-standard ::after ::backdrop ::before ::checkmark Experimental ::column Experimental ::cue ::details-content ::file-selector-button ::first-letter ::first-line ::grammar-error ::highlight() ::marker ::part() ::picker-icon Experimental ::picker() Experimental ::placeholder ::scroll-* ::scroll-button() Experimental ::scroll-marker Experimental ::scroll-marker-group Experimental ::selection ::slotted() ::spelling-error ::target-text ::view-* ::view-transition ::view-transition-group() ::view-transition-image-pair() ::view-transition-new() ::view-transition-old() At-rules @charset @color-profile @container @counter-style @custom-media Experimental @document Non-standard Deprecated @font-face @font-feature-values @font-palette-values @function Experimental @import @keyframes @layer @media @namespace @page @position-try @property @scope @starting-style @supports @view-transition Values !important fit-content inherit initial max-content min-content revert revert-layer rule-list unset Types <absolute-size> <alpha-value> <angle-percentage> <angle> <axis> <baseline-position> <basic-shape> <blend-mode> <box-edge> <calc-keyword> <calc-sum> <color-interpolation-method> <color> <content-distribution> <content-position> <corner-shape-value> Experimental <custom-ident> <dashed-function> Experimental <dashed-ident> <dimension> <display-box> <display-inside> <display-internal> <display-legacy> <display-listitem> <display-outside> <easing-function> <filter-function> <flex> <frequency-percentage> <frequency> <generic-family> <gradient> <hex-color> <hue-interpolation-method> <hue> <ident> <image> <integer> <length-percentage> <length> <line-style> <named-color> <number> <overflow-position> <overflow> <percentage> <position-area> <position> <ratio> <relative-size> <resolution> <self-position> <shape> Deprecated <string> <system-color> <text-edge> <time-percentage> <time> <timeline-range-name> <transform-function> <url> Functions -moz-image-rect Non-standard Deprecated abs() acos() anchor-size() anchor() asin() atan() atan2() attr() blur() brightness() calc-size() Experimental calc() circle() clamp() color-mix() color() conic-gradient() contrast-color() contrast() cos() counter() counters() cross-fade() cubic-bezier() device-cmyk() drop-shadow() dynamic-range-limit-mix() Experimental element() Experimental ellipse() env() exp() fit-content() grayscale() hsl() hue-rotate() hwb() hypot() if() Experimental image-set() image() inset() invert() lab() lch() light-dark() linear-gradient() linear() log() matrix() matrix3d() max() min() minmax() mod() oklab() oklch() opacity() paint() path() perspective() polygon() pow() progress() radial-gradient() ray() rect() rem() repeat() repeating-conic-gradient() repeating-linear-gradient() repeating-radial-gradient() rgb() rotate() rotate3d() rotateX() rotateY() rotateZ() round() saturate() scale() scale3d() scaleX() scaleY() scaleZ() sepia() shape() sibling-count() sibling-index() sign() sin() skew() skewX() skewY() sqrt() steps() superellipse() Experimental symbols() tan() translate() translate3d() translateX() translateY() translateZ() type() Experimental url() var() xywh() Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://www.fine.dev/blog/create-soft-delete-with-ai | Using AI for backend feature development: Implementing Soft Delete Home Docs Changelog Pricing Sign in Get started -> Menu Home Docs Changelog Pricing <- Go Back Using AI for backend feature development: Implementing Soft Delete Backend development often involves managing user data efficiently, and implementing features like soft delete is crucial for preserving data without permanent loss. With Fine, developers can easily delegate such tasks to AI, saving time and focusing on what truly matters—building great products. "Soft Delete" is an important feature and needs to be prioritized - but it's not going to improve customer satisfaction or sales in the short term, so being able to delegate it and keep your developers focused on other high-value tasks is ideal for small dev teams. Let's explore how Fine can help add a "Soft Delete" feature for user accounts in a backend application. The Challenge: Adding a Soft Delete Feature for User Accounts Adding a "deleted_at" timestamp to mark user accounts as inactive. Updating ORM queries to exclude soft-deleted users. Modifying API endpoints to support soft delete without affecting existing functionality. Ensuring changes are tested in a secure, isolated environment. For many startups, handling data effectively while minimizing the risk of data loss is a high priority. However, implementing soft delete can be time-consuming and require careful adjustments across the database, application logic, and API layers. How Fine Simplifies the Process Fine streamlines soft delete implementation with its intelligent automation capabilities. Here's how it helps: Generates a Migration Script Fine creates a PostgreSQL migration script to add the "deleted_at" column to the users table, allowing for efficient marking of inactive accounts. Updates ORM Queries It updates all ORM queries in your codebase to exclude users where "deleted_at" is not null, maintaining clean and accurate query results. Modifies API Endpoints Fine modifies the GET /users API endpoint to support an optional "include_deleted" parameter, enabling flexible retrieval of both active and soft-deleted users. Tests Changes in a Virtual Machine The AI agent runs tests in an isolated virtual machine, ensuring that all changes are verified without impacting the live environment. Prompt Used To implement a soft delete feature, simply provide Fine with the following prompt: Generate a PostgreSQL migration script to add a deleted_at timestamp column to the @users table. Update all ORM queries in our codebase to exclude records where deleted_at is not null, and modify the GET /users API endpoint to support an optional include_deleted parameter. Fine will handle the heavy lifting, delivering fully functional scripts, queries, and modifications in moments. Benefits of Using Fine By leveraging Fine for implementing a soft delete, developers gain: Non-Destructive Data Handling Soft delete ensures that data is not permanently removed, allowing for better control and recovery options. Maintained Data Integrity Automation helps maintain data integrity by ensuring all ORM queries and endpoints are consistently updated. Improved Developer Efficiency Automation reduces manual coding, allowing developers to focus on innovation and other critical tasks. Tested in a Safe Environment Fine runs the changes in a sandbox environment, providing live previews and ensuring stability before deployment. Conclusion: Fine – Your Go-To for Simplified Backend Development With Fine, adding a soft delete feature to your backend app is straightforward. From generating migration scripts to updating queries and modifying endpoints, Fine empowers developers to implement non-destructive features with minimal effort. Ready to streamline your backend development? Try Fine and see the difference it can make. Start building today Try out the smoothest way to build, launch and manage an app Try for Free -> © Fine.dev - All rights reserved. Product Overview AI Workflows Pricing & Plans Changelog Blog Docs Company Press Terms & Conditions Privacy policy | 2026-01-13T08:48:26 |
https://jobs.dev.to | Jobs at DEV - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Jobs at DEV About Forem Forem is a company committed to empowering community. We operate DEV , CodeNewbie , and our underlying platform, Forem . DEV is the first social network built with Forem, where software developers of all backgrounds and experience levels can connect and share knowledge with one another. DEV was founded on the idea that the software developer ecosystem needed a true community platform that extended beyond code collaboration tools and troubleshooting forums. Forem , the open-source software that powers DEV, is a platform established on trust and transparency that does not track users, centralize control, or hoard user data. As an open-source platform, every line of code is auditable by the community itself. Each community controls its own data, domain, and develops its own brand, with no central authority or internet overlords. Current Openings No current openings, check back later! 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/templates#adding-dynamic-content | Design Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Templates Design Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Templates Design Template OpenAI Open in ChatGPT How to create, manage, and test templates in SuprSend. OpenAI Open in ChatGPT Templates are the content block of your notification. In SuprSend, content for all channels (SMS, email, chat, push etc.) is grouped under a single template group for simplified management. Your template can have 2 types of content: Static Content : This remains the same for all users and contains your core message or design. Dynamic Content : These are placeholders for user or tenant-specific information, such as first names, booking amounts, appointment times, and more. The variables are populated dynamically based on the data provided in your workflow or event request. Benefits of Using Templates with SuprSend Unified Content Management : Content for all channels is grouped together in a single template, making it easy to manage your content in one place. WYSWYG editors : Designing a template is a piece of cake with drag-and-drop and form editors. Your product managers and designers can take control of content creation without involving developers. Multi-Lingual support: You can add content for multiple languages in a single template and the user will receive notification in their preferred language Create white-labeled notifications for your tenants with ease : You can create tenants for your own company and each of your tenants. Use it to dynamically change your email template styling to match the tenant’s identity. Easy to iterate : You can directly design and store templates on the SuprSend dashboard, decoupling templates from your code. Version control : Each template change is published as a new version, so you can always track historical changes. You can also monitor user engagement for each version and retain the one that performs better. Trigger a test notification on your current live version to see the content preview on your actual device before pushing it to production. Add / Remove channels without touching code : To add any channel to your existing template group, you need to simply design a template for that channel on SuprSend platform and publish it. Notifications will start going through that channel, with no alterations to your existing code. Create Template SuprSend’s template designer empowers you to create beautiful templates with easy drag-and-drop editor 1 Create a template Add a template name and Click on ‘ Save ’. The new Template will be created, which you can see on the top of ‘Templates’ listing page. Click on the template to start editing. 2 Select the Channel Select the channel that you want to edit and enable it. 3 Add template content You can get the detailed guide to design the template for each channel in their respective documents: Email SMS Inbox Push channels: Android Push iOSpush Web Push Chat: Slack WhatsApp MS Teams Template versions SuprSend creates a new version every time you publish a template. This is to ensure that you have historical reference to all the changes done in your template. Helps with audit trails and understanding which template content performed better in terms of user engagement. A draft version is created by default. You’ll always do your changes in the draft version and publish the template once finalized. The recent published template will become the live version . All your notifications will be using the live template version. Earlier published versions will become inactive as soon as you publish a new template. You can see inactive template versions by selecting ‘ All ’ tab from the top right side options. Adding variable content SuprSend supports dynamic templating so you can personalize notifications using data from your workflow, user profile, and tenant settings. Templates use two languages: Handlebars — Email, SMS, WhatsApp, and Inbox JSONNET — Slack and MS Teams To start using dynamic variables, first add sample data in the Mock Data panel of the template editor. 1. Add mock data Mock data helps you: Define the structure of variables up front, reducing mismatches between the template and actual payload. Get auto-suggestions while designing templates, avoiding typos. Consistently reuse the same variables across all channels within a template. Preview the final rendered notification and send test messages using sample values. Sample mock data: json Copy Ask AI { "name" : "Steve" , "items" : [ { "item" : "Jager-Smith Premium" , "tracking_id" : "FMPP14677458796" , "delivery_date" : "22 June, 2023" }, { "item" : "Winget Women Cap" , "tracking_id" : "FMPP7734374844765" , "delivery_date" : "23 June, 2023" } ], "amount" : "$3,249" , "tracking_link" : "https://www.example.com/track" } 2. Available data types and their syntax There are four primary sources of dynamic data you can pull into your templates. Input Payload This includes: Data from your trigger payload Data added or modified during the workflow via data transform, batch/digest, webhook/fetch, etc. Referring this data in the template as: Data Type Handlebars JSONNET Parent level keys {{var1}} data.var1 Nested keys {{var1.var2.var3}} data.var1.var2.var3 Array index {{var1.[0].name}} data.var1[0].name Keys with capital letters and spaces {{[first_name]}} data['first_name'] Batching data {{$batched_events_count}} data['$batched_events_count'] For more advanced logic or complex functions, refer to the full set of available options in the Handlebars Helpers documentation . Please wrap URLs or variables that may contain special characters in triple curly braces (e.g., {{{url}}} ). Using double braces triggers HTML-escaping in Handlebars, which may alter special characters. User properties For per-user personalization, you can use user properties in your templates. These properties are automatically available from each user’s profile and can be referenced using $user , $actor or $recipient variables. Handlebars JSONNET $user.name data['$user'].name $recipient.name data['$recipient'].name $actor.name data['$actor'].name Tenant properties If you are using tenant branding, you can include tenant properties in your templates to dynamically display details such as logo, address, and colors. The email designer also provides a Tenant component with pre-designed header, footer, and button, making it easier for you to add tenant branding to your templates. Handlebars JSONNET $tenant.name data['$tenant'].name $tenant.properties.address data['$tenant'].properties.address Preview and publish You can see the notification preview on the right side of your editor for most of the channels. Variables in template are replaced with the values from ‘ mock data’ for preview For email , preview option is available in the bottom left side menu For Slack , you can click on ‘ Load preview ’ button to see the preview Once finalized, you can publish the template by clicking on ‘ Publish template ’ button on the draft version Test template You can send test notifications directly from the template editor page to see how the message will appear on user’s device. To send a test notification, 1 Click on the "Test" button You can find the Test button on the top right corner. 2 Add Distinct ID Add the distinct_id of the user , and click on search. It will show all the available channels for the user. 3 Choose the relevant channels Select those channels on which you’d like to test, and then click on Trigger Test using mock data . This will trigger a test notification. 4 Go to Logs You can go to the logs in order to monitor the real-time status of your sent notification. JSON data added in the global “Mock Data” button will be used to render variables in the template. Make sure to add mock data for all the variables added in the template else notifications will fail. ** Defining template in your workflow request ** The serves as a unique identifier for referencing a template in workflows created through API . To copy the slug name, click on the clipboard next to the Template name. ** Edit template name and other details ** You can edit the template description, name, and add tags to the template by clicking on the edit icon next to the its name. We recommend adding your template trigger logic and other relevant notes pertaining to the notification in the description . This is helpful for later reference and note keeping. Tags are used for better organization of the templates on listing page. You can group similar templates using tags. Tags can then be used to filter out templates on listing page and also while fetching templates through API . Clone template To avoid designing templates from scratch, you can clone your existing templates and design on top of it. Adding multiple languages SuprSend allows you to create notifications in multiple languages in the same template. Once the languages are added, SuprSend will pick the preferred language from user’s profile and send the message as per the user’s preferred language. You can add template languages using Language option from the top-right corner burger menu. For more details, check steps and guidelines on adding language . Archive template You can archive your unused templates by clicking on “Archive” option from the top-right corner burger menu. Templates can’t be recovered once archived. View and filter your template list All of your active templates will be visible on the template listing page. You can filter your templates by channel , tag , status or just get the templates which were ‘ edited by you’ . Archived templates can be seen by clicking on Archived tab from the top right side options Was this page helpful? Yes No Suggest edits Raise issue Previous Email Template How to design email template using either drag and drop editor or code editor. Next ⌘ I x github linkedin youtube Powered by On this page Create Template Template versions Adding variable content 1. Add mock data 2. Available data types and their syntax Input Payload User properties Tenant properties Preview and publish Test template Clone template Adding multiple languages Archive template View and filter your template list | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/node-lists | Lists - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Integrate Node SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Java SDK Go SDK SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Node.js SDK Lists Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Node.js SDK Lists OpenAI Open in ChatGPT Manage subscriber lists with NodeJS SDK: create/update list, add/remove/replace users. OpenAI Open in ChatGPT The Lists SDK methods lets you create / manage list of subscribers. You can then send broadcast to all the users in the list or create a workflow that triggers when a new user enters / exits list. Create / Update List You can use supr_client.subscribers_list.create method to create a new list Request Response Copy Ask AI const { Suprsend } = require ( "@suprsend/node-sdk" ); const supr_client = new Suprsend ( "workspace_key" , "workspace_secret" ); // create list API call const response = supr_client . subscriber_lists . create ({ list_id: "_list_id_" , list_name: "_list_name_" , list_description: "_some sample descritpion for list_" , }); data . then (( res ) => console . log ( res )). catch (( err ) => console . log ( err )); Guidelines on defining the list_id list_id is case-insensitive. Suprsend first converts list_id to lowercase before storing it or doing any sort of comparison on it. list_id can be of max 64 characters. It can contain characters [a-z0-9_-] that is alphanumeric characters, _(underscore) and -(hyphen). Get list data You can get the latest information of a list using supr_client.subscribers_list.get method. Request Response Copy Ask AI const data = supr_client . subscriber_lists . get ( "_list_id_" ); Get list of lists To get the data of all the lists created in your workspace, use supr_client.subscribers_list.get_all() method Request Response Copy Ask AI const data = supr_client . subscriber_lists . get_all (); // default limit 20 const data = supr_client . subscriber_lists . get_all ({ limit: 20 , offset: 0 }); // max limit 1000 Add subscribers to list Use supr_client.subscribers_list.add() to add list subscribers. There is no limit to the number of subscribers that you can add to a list. Request Response Copy Ask AI const list_id = "_list_id_" ; const subscribers = [ "_distinct_id1_" , "_distinct_id2_" , ... .. ]; const data = supr_client . subscriber_lists . add ( list_id , subscribers ); Remove subscribers from list You can remove subscribers from the list using supr_client.subscribers_list.remove() Request Response Copy Ask AI const list_id = "_list_id_" ; const subscribers = [ "_distinct_id1_" , "_distinct_id2_" , ... .. ]; const data = supr_client . subscriber_lists . remove ( list_id , subscribers ); Delete list Request Copy Ask AI const data = supr_client . subscriber_lists . delete ( "_list_id_" ); Replace users in the list In case you want to refresh list with a new set of users completely, you can replace users by creating a draft version of the list and updating users in it. 1 Start Sync to create draft version of the list This method will create a draft version of the list where you can add the new set of users to replace users. Request Copy Ask AI const data = supr_client . subscriber_lists . start_sync ( "_list_id_" ); 2 Add Subscribers to draft list You can use this method to add subscribers to List draft version created in the Step-1. You’ll get version_id in start sync response. Request Copy Ask AI const data = supr_client . subscriber_lists . add_to_version ( "_list_id_" , "01HHCTXXXXXXXXXXX" , [ "_user_id_1" , "user_id_2" ]) 3 Remove Subscribers from draft list You can use this method to remove subscribers from List draft version created in Step-1. You’ll get version_id in start sync response. Request Copy Ask AI const data = supr_client . subscriber_lists . remove_from_version ( "_list_id_" , "01HHCTXXXXXXXXXXX" , [ "_user_id_1" , "_user_id_2" ]) 4 Finish Sync to make the draft version live Once your subscribers are updated in the list, use this method to finish sync and make the draft version updated in above steps live. Request Copy Ask AI const data = supr_client . subscriber_lists . finish_sync ( "_list_id_" , "01HHCTXXXXXXXXXXX" ) Delete draft list You can also delete draft list if it’s created by mistake. Request Copy Ask AI const data = supr_client.subscriber_lists.delete_version( "_list_id_" , "01HHCTXXXXXXXXXXX" ) ; Was this page helpful? Yes No Suggest edits Raise issue Previous Broadcast Trigger broadcast notifications to a list of users with NodeJS SDK. Next ⌘ I x github linkedin youtube Powered by On this page Create / Update List Get list data Get list of lists Add subscribers to list Remove subscribers from list Delete list Replace users in the list Delete draft list | 2026-01-13T08:48:26 |
https://developer.mozilla.org/en-US/docs/Web/Security | Security on the web | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web Security Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Security on the web Websites contain several different types of information. Some of it is non-sensitive, for example the copy shown on the public pages. Some of it is sensitive, for example customer usernames, passwords, and banking information, or internal algorithms and private product information. Sensitive information needs to be protected, and that is the focus of web security. If that information fell into the wrong hands, it could be used to: Put companies at a competitive disadvantage by sharing their information with competitors. Disable or hijack their services, again causing serious problems with their operation. Put their customer's privacy at risk, making them vulnerable to profiling, targeting, loss of data, identity theft, or even financial loss. Modern browsers already have several features to protect users' security on the web, but developers also need to use best practices and code carefully to ensure that their websites are secure. Even simple bugs in your code can result in vulnerabilities that bad actors can exploit to steal data and gain unauthorized control over services. This article provides an introduction to web security, including conceptual information to help you understand website vulnerabilities and practical guides on how to secure them. In this article Relationship between security and privacy Security features provided by browsers High-level security considerations Practical security implementation guides See also Relationship between security and privacy Security and privacy are distinct yet closely related topics. It is worth knowing the differences between the two and how they relate. Security is the act of keeping private data and systems protected against unauthorized access. This includes both company (internal) data and user and partner (external) data. Privacy refers to the act of giving users control over how their data is collected, stored, and used, while also ensuring that it is not used irresponsibly. For example, you should let your users know what data you are collecting from them, the parties with whom it will be shared, and how it will be used. Users must be given a chance to consent to your privacy policy, have access to their data you store, and delete it if they choose to. Good security is essential for good privacy. You could follow all the advice listed in our Privacy on the web guide, but acting with integrity and having a robust privacy policy are futile if your site is not secure and attackers can just steal data anyway. Security features provided by browsers Web browsers follow a strict security model that enforces strong security for content, connections between the browser and the server, and data transportation. This section looks at the features that underpin this model. Same-origin policy and CORS Same-origin policy is a fundamental security mechanism of the web that restricts how a document or a script loaded from one origin can interact with a resource from another origin. It helps isolate potentially malicious documents, reducing possible attack vectors. In general, documents from one origin cannot make requests to other origins. This makes sense because you don't want sites to be able to interfere with one another and access unauthorized data. However, you might want to relax this restriction in some circumstances; for example, if you have multiple websites that interact with each other, you may allow them to request resources from one another using fetch() . This can be permitted using Cross-Origin Resource Sharing (CORS) , an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. HTTP model for communication The HTTP protocol is used by web browsers and servers to communicate with one another, request resources, provide responses (for example, providing a requested resource or detailing why a request failed), and provide security features for that communication. Transport Layer Security (TLS) provides security and privacy by encrypting data during transport over the network and is the technology behind the HTTPS protocol. TLS is good for privacy because it stops third parties from being able to intercept transmitted data and use it maliciously. All browsers are moving towards requiring HTTPS by default; this is practically the case already because you can't do much on the web without this protocol. Related topics: Transport layer security (TLS) The TLS protocol is the standard for enabling two networked applications or devices to exchange information privately and robustly. Applications that use TLS can choose their security parameters, which can have a substantial impact on the security and reliability of data. HTTP Strict-Transport-Security The Strict-Transport-Security HTTP header lets a website specify that it may only be accessed using HTTPS. Certificate Transparency Certificate Transparency (CT) is an open framework designed to protect against and monitor for certificate misissuance. Newly issued certificates are 'logged' to publicly run, often independent CT logs. These provide append-only, cryptographically assured records of issued TLS certificates. Mixed content An HTTPS page that includes content fetched using cleartext HTTP is called a mixed content page. Pages like this are only partially encrypted, leaving the unencrypted content accessible to sniffers and man-in-the-middle attackers. Secure contexts and feature permissions Browsers control the usage of "powerful features" in different ways. These "powerful features" include generating system notifications on a website, using a user's webcam to get access to a media stream, manipulating the system GPU, and using web payments. If a site could just use the APIs that control such features without restriction, malicious developers could attempt to do the following: Annoy users with unneeded notifications and other UI features. Turn their webcam on without warning to spy on them. Clog up their browser/system to create Denial of Service (DoS) attacks. Steal data or money. These "powerful features" are controlled in the following ways: Usage of such features is permitted only in secure contexts . A secure context is a window or a worker for which there is reasonable confidence that the content has been delivered securely (via HTTPS/TLS). In a secure context, the potential for communication with contexts that are not secure is limited. Secure contexts also help to prevent man-in-the-middle attackers from accessing powerful features. To see a list of web platform features available only in secure contexts, see Features restricted to secure contexts . The usage of these features is gated behind a system of user permissions: users have to explicitly opt-in to providing access to such features, meaning that they can't be used automatically. User permission requests happen automatically, and you can query the state of an API permission by using the Permissions API . Several other browser features can be used only in response to a user action such as clicking a button, meaning that they need to be invoked from inside an appropriate event handler. This is called transient activation . See Features gated by user activation for more information. High-level security considerations There are many aspects of web security that need to be thought about on the server- and client-side. This section focuses mainly on client-side security considerations. You can find a useful summary of security from a server-side perspective, which also includes descriptions of common attacks to watch out for, at Website security (part of our Server-side website programming learning module). Store client-side data responsibly Handling data responsibly is largely concerned with cutting down on third-party cookie usage and being careful about the data you store and share with them. Traditionally, web developers have used cookies to store all kinds of data, and it has been easy for attackers to exploit this tendency. As a result, browsers have started to limit what you can do with cross-site cookies, with the aim of removing access to them altogether in the future. You should prepare for the removal of cross-site cookies by limiting the amount of tracking activities you rely on and/or by implementing the persistence of the desired information in other ways. See Transitioning from third-party cookies for more information. Protect user identity and manage logins When implementing a secure solution that involves data collection, particularly if the data is sensitive such as log-in credentials, it makes sense to use a reputable solution. For example, any respectable server-side framework will have built-in features to protect against common vulnerabilities. You could also consider using a specialized product for your purpose, for example an identity provider solution or a secure online survey provider. If you want to roll your own solution for collecting user data, make sure you understand all aspects and requirements. Hire an experienced server-side developer and/or security engineer to implement the system, and ensure it is tested thoroughly. Use multi-factor authentication (MFA) to provide better protection. Consider using a dedicated API such as Web Authentication or Federated Credential Management to streamline the client-side of the app. Here are some other tips for providing secure logins: When collecting user login information, enforce strong passwords so that your user's account details cannot be easily guessed. Weak passwords are one of the main causes of security breaches. In addition, encourage your users to use a password manager so that they can use more complex passwords, don't need to worry about remembering them, and won't create a security risk by writing them down. See also our article on password authentication . You should also educate your users about phishing . Phishing is the act of sending a message to a user (for example, an email or an SMS) containing a link to a site that looks like a site they use every day but isn't. The link is accompanied by a message designed to trick users into entering their username and password on the site so it can be stolen and then used by an attacker for malicious purposes. Note: Some phishing sites can be very sophisticated and hard to distinguish from a real website. You should therefore educate your users to not trust random links in emails and SMS messages. If they receive a message along the lines of "Urgent, you need to log in now to resolve an issue", they should go to the site directly in a new tab and try logging in directly rather than clicking the link in the message. Or they could phone or email you to discuss the message they received. Protect against brute force attacks on login pages with rate limiting , account lockouts after a certain number of unsuccessful attempts, and CAPTCHA challenges . Manage user login sessions with unique session IDs , and automatically log out users after periods of inactivity. Don't include sensitive data in URL query strings As a general rule, you shouldn't include sensitive data in URL query strings because if a third party intercepts the URL (for example, via the Referer HTTP header), they could steal that information. Even more serious is the fact that these URLs can be indexed by public web crawlers, HTTP proxies, and archiving tools such as the internet archive , meaning that your sensitive data could persist on publicly accessible resources. Use POST requests rather than GET requests to avoid these issues. Our article Referer header policy: Privacy and security concerns describes in more detail the privacy and security risks associated with the Referer header, and offers advice on mitigating those risks. Note: Steering away from transmitting sensitive data in URLs via GET requests can also help protect against cross-site request forgery and replay attacks . Enforce usage policies Consider using web platform features like Content Security Policy (CSP) and Permissions Policy to enforce a set of feature and resource usage rules on your website that make it harder to introduce vulnerabilities. CSP allows you to add a layer of security by, for example, allowing images or scripts to be loaded only from specific trusted origins. This helps to detect and mitigate certain types of attacks, including Cross-Site Scripting ( XSS ) and data injection attacks. These attacks involve a range of malicious activities, including data theft, site defacement, and distribution of malware. Permissions policy works in a similar way, except that it is more concerned with allowing or blocking access to specific "powerful features" ( as mentioned earlier ). Note: Such policies are very useful to help keep sites secure, especially when you are using a lot of third-party code on your site. However, keep in mind that if you block usage of a feature that a third-party script relies on to work, you may end up breaking your site's functionality. Maintain data integrity Following on from the previous section, when you allow feature and resource usage on your site, you should try to ensure that resources have not been tampered with. Related topics: Subresource integrity Subresource Integrity (SRI) is a security feature that enables browsers to verify that resources they fetch (for example, from a CDN ) are delivered without unexpected manipulation. It works by allowing you to provide a cryptographic hash that a fetched resource must match. HTTP Access-Control-Allow-Origin The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin . HTTP X-Content-Type-Options The X-Content-Type-Options response header is a marker used by the server to indicate that the MIME types advertised in the Content-Type headers should not be changed and must be followed. This header is a way to opt out of MIME type sniffing , or, in other words, to specify that the MIME types are deliberately configured. Sanitize form input As a general rule, don't trust anything that users enter into forms. Filling out forms online is complicated and tedious, and it is easy for users to enter incorrect data or data in the wrong format. In addition, malicious folks are skilled in the art of entering specific strings of executable code into form fields (for example, SQL or JavaScript). If you're not careful about handling such inputs, they could either execute harmful code on your site or delete your databases. See SQL injection for a good example of how this could happen. To protect against this, you should thoroughly sanitize data entered into your forms: You should implement client-side validation to inform users when they have entered data in the wrong format. You can do this using built-in HTML form validation features, or you can write your own validation code. See Client-side form validation for more information. You should use output encoding when displaying user input in an application UI to safely display data exactly as a user typed it in and avoid it being executed as code. See Output encoding for more information. You can't rely on client-side validation alone for security — it should be combined with server-side validation. Client-side validation enhances the user experience by providing instant validation feedback without having to wait for a round trip to the server. However, client-side validation is easy for a malicious party to bypass (for example, by turning off JavaScript in the browser to bypass JavaScript-based validation). Any reputable server-side framework will provide functionality for validating form submissions. In addition, a common best practice is to escape any special characters that form part of executable syntax, thereby making any entered code no longer executable and treated as plain text. Protect against clickjacking In a clickjacking attack, a user is fooled into clicking a UI element that performs an action different from what the user expects, often resulting in the user's confidential information being passed to a malicious third party. This risk is inherent in embedded third-party content, so make sure you trust what is being embedded into your site. Additionally, be aware that clickjacking can be combined with phishing techniques. You can read about phishing in the previous section Protect user identity and manage logins . The following features can help guard against clickjacking: HTTP X-Frame-Options The X-Frame-Options HTTP response header can be used to indicate whether a browser should be allowed to render a page in a <frame> , <iframe> , <embed> or <object> . Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites. CSP: frame-ancestors The HTTP Content-Security-Policy (CSP) frame-ancestors directive specifies valid parents that may embed a page using <frame> , <iframe> , <object> , or <embed> . Practical security implementation guides To get comprehensive instructions for implementing security features effectively on websites and to ensure you're following best practices, see our set of Practical security implementation guides . Some of these guides are directly related to the HTTP Observatory tool. Observatory performs security audits on a website and provides a grade and score along with recommendations for fixing the security issues it finds. These guides explain how to resolve issues surfaced by the MDN Observatory tests: the tool links to the relevant guide for each issue, helping guide you towards an effective resolution. Interestingly, Mozilla's internal developer teams use this guidance when implementing websites to ensure that security best practices are applied. See also Privacy on the web Learn: Website security Mozilla Security Blog OWASP Cheat Sheet series Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 3, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Security Guides Attacks Clickjacking Cross-site leaks (XS-Leaks) Cross-site request forgery (CSRF) Cross-site scripting (XSS) Insecure Direct Object Reference (IDOR) JavaScript prototype pollution Manipulator in the Middle (MITM) Phishing Server Side Request Forgery (SSRF) Subdomain takeover Supply chain attacks Defenses Certificate Transparency Mixed content Same-origin policy Secure contexts Subresource Integrity Transport Layer Security User activation Authentication Federated identity One-time passwords (OTP) Passwords Practical implementation guides Content Security Policy (CSP) Cross-Origin Resource Policy (CORP) Cross-Origin Resource Sharing (CORS) How to turn off form autocompletion MIME type verification Referrer policy robots.txt configuration Secure cookie configuration Subresource integrity (SRI) Transport Layer Security (TLS) Firefox security guidelines Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:26 |
https://docs.suprsend.com/docs/react-sdk#content-area | SDK Integration - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK SuprSend Client SDK Authentication Javascript Android iOS React Native Flutter React SDK Integration WebPush Preferences Events and User methods InApp Feed Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation React SDK Integration Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog React SDK Integration OpenAI Open in ChatGPT SDK Integration to enable SuprSend features like Inbox, Preferences, and Webpush into React-based web applications. OpenAI Open in ChatGPT Installation We support 2 SDK’s for react based applications. @suprsend/react-core : This provides context providers and hooks to integrate SuprSend in to your application. If you want to use web-push, user methods, track events or implement your own UI for preferences and inbox by using provided methods, this library is better option. If you want to use any of inbuilt components for inbox or preferences then use @suprsend/react . @suprsend/react : This library is built on top of @suprsend/react-core , so all hooks, context providers and methods that are present in @suprsend/react-core library are also present in this, with addition to that drop-in components like Inbox, NotificationsFeed, Preferences etc are available which comes with UI to ease integration. npm yarn Copy Ask AI npm install @ suprsend / react Integration SuprSendProvider This context provider need to be wrapper around your component in which you want to use SuprSend methods. This is responsible for creating client instance( new SuprSend() ), identify and reset user. You can access the SuprSend client instance using useSuprSendClient hook. This instance contains all methods needed to integrate preferences, webpush, track events and user methods. Example.js TypeDef Copy Ask AI import { SuprSendProvider } from '@suprsend/react' ; function Example () { return ( < SuprSendProvider publicApiKey = { YOUR_KEY } distinctId = { YOUR_DISTINCT_ID } > < MyComponent /> </ SuprSendProvider > ); } Parameter Description publicApiKey public API Key is mandatory field without which error will be thrown by SuprSendProvider. You can get this from SuprSend Dashboard . distinctId Unique identifier to identify a user across platform. If a value is passed SDK will create user and authenticate user. If null value is passed authenticated user’s instance data will be cleared in your application, kind of logout. userToken Mandatory when enhanced security mode is on. This is ES256 JWT token generated in your server-side. Refer docs to create userToken. refreshUserToken This function is called by SDK internally to get new userToken before existing token is expired. The returned JWT token string is used as the new userToken. userAuthenticationHandler This callback will be called after authenticating user internally when you pass distinctId field to give you back the response of user creation API call. host Customise the host url. vapidKey This key is needed only if you are implementing WebPush notifications. You can get it in SuprSend Dashboard —> Vendors —> WebPush swFileName This key is needed only if you are implementing WebPush notifications and want to customise default serviceworker.js file name with your own service worker file name. After implementing the above SuprSendProvider you can be able to use all SuprSend features. useSuprSendClient This hook is used to access internal SuprSend client instance which has all methods related to webpush, preferences, user methods and track event. Use this hook inside child of SuprSendProvider. Example.js Copy Ask AI import { SuprSendProvider , useSuprSendClient } from "@suprsend/react" function Example () { return ( < SuprSendProvider publicApiKey = { YOUR_KEY } distinctId = { YOUR_DISTINCT_ID } > < MyComponent /> </ SuprSendProvider > ); } function MyComponent () { const suprSendClient = useSuprSendClient (); return ( < p onClick = { () => { // suprSendClient.track('testing'); // suprSendClient.user.setEmail(' [email protected] ') // suprSendClient.webpush.registerPush() // suprSendClient.user.preferences.getPreferences() } } > Click Me </ p > ); } useAuthenticateUser This hook is used to get authenticated user anywhere in your application inside SuprSendProvider. This can also be used to check if user is authenticated before calling any method of SuprSend. Example.js Copy Ask AI import { useAuthenticateUser } from '@suprsend/react' ; function MyComponent () { const { authenticatedUser } = useAuthenticateUser (); useEffect (() => { if ( authenticatedUser ) { console . log ( 'User is authenticated' , authenticatedUser ); } }, [ authenticatedUser ]); return < p > Hello world </ p > ; } Was this page helpful? Yes No Suggest edits Raise issue Previous WebPush Integration steps of webpush in react application. Next ⌘ I x github linkedin youtube Powered by On this page Installation Integration SuprSendProvider useSuprSendClient useAuthenticateUser | 2026-01-13T08:48:26 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.