{"id":1110,"date":"2017-07-25T12:58:25","date_gmt":"2017-07-25T12:58:25","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=1110"},"modified":"2025-10-23T02:21:20","modified_gmt":"2025-10-23T06:21:20","slug":"inspecting-elements-mozilla-chrome-ie","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/inspecting-elements-mozilla-chrome-ie\/","title":{"rendered":"Inspecting elements in mozilla chrome and IE"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><strong>Why Inspecting Elements Matters in Selenium Testing<\/strong><\/h2>\n\n\n\n<p>Imagine you\u2019re automating a login test on a website using Selenium. Your script clicks buttons, enters credentials, and validates results all without human input. But have you ever wondered how Selenium knows <em>which<\/em> button to click or <em>where<\/em> to type the password?<\/p>\n\n\n\n<p>The answer lies in <strong>inspecting elements<\/strong> the process of examining HTML code in browsers like Mozilla Firefox, Google Chrome, or Internet Explorer (IE) to locate web elements precisely.<\/p>\n\n\n\n<p>In Selenium testing, inspecting elements forms the backbone of every automation script. Whether you\u2019re learning through a <a href=\"https:\/\/www.h2kinfosys.com\/courses\/selenium-automation-testing-certification-course\/\" data-type=\"link\" data-id=\"https:\/\/www.h2kinfosys.com\/courses\/selenium-automation-testing-certification-course\/\">Selenium certification course<\/a> or pursuing a Selenium course online, understanding how to inspect elements accurately is your first major step toward building efficient test scripts.<\/p>\n\n\n\n<p>In this guide, we\u2019ll explore how to inspect elements across different browsers Mozilla Firefox, Google Chrome, and Internet Explorer along with best practices, shortcuts, and real-world examples that make automation easier and faster.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Does Inspecting Elements Mean?<\/strong><\/h2>\n\n\n\n<p>Before diving into browser-specific details, let\u2019s clarify the concept.<\/p>\n\n\n\n<p>Inspecting elements is the process of viewing and analyzing the HTML and CSS structure of a web page. Each button, image, textbox, or link on a webpage is represented in the Document Object Model (DOM).<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img fetchpriority=\"high\" decoding=\"async\" width=\"800\" height=\"400\" src=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2017\/07\/chrome-inspect-element-hero.png\" alt=\"Inspecting elements\" class=\"wp-image-31201\" title=\"\" srcset=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2017\/07\/chrome-inspect-element-hero.png 800w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2017\/07\/chrome-inspect-element-hero-300x150.png 300w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2017\/07\/chrome-inspect-element-hero-768x384.png 768w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/figure>\n\n\n\n<p>By inspecting elements, testers can:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Identify attributes like <code>id<\/code>, <code>name<\/code>, <code>class<\/code>, or <code>xpath<\/code><\/li>\n\n\n\n<li>Understand how an element is structured within the HTML<\/li>\n\n\n\n<li>Validate whether locators used in Selenium scripts are correct<\/li>\n\n\n\n<li>Debug failed test cases related to incorrect element identification<\/li>\n<\/ul>\n\n\n\n<p>In short, inspecting elements bridges the gap between the <em>visual interface<\/em> you see and the <em>underlying code<\/em> Selenium interacts with.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The Role of Inspecting Elements in Selenium Automation<\/strong><\/h2>\n\n\n\n<p>Selenium interacts with web pages using locators such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>ID<\/strong><\/li>\n\n\n\n<li><strong>Name<\/strong><\/li>\n\n\n\n<li><strong>Class Name<\/strong><\/li>\n\n\n\n<li><strong>Tag Name<\/strong><\/li>\n\n\n\n<li><strong>Link Text<\/strong><\/li>\n\n\n\n<li><strong>Partial Link Text<\/strong><\/li>\n\n\n\n<li><strong>CSS Selector<\/strong><\/li>\n\n\n\n<li><strong>XPath<\/strong><\/li>\n<\/ul>\n\n\n\n<p>When you inspect an element, you extract these locators and feed them into your Selenium script.<\/p>\n\n\n\n<p>For example:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">from selenium import webdriver\n\ndriver = webdriver.Chrome()\ndriver.get(\"https:\/\/example.com\/login\")\n\n# Inspecting elements to find locators\ndriver.find_element(\"id\", \"username\").send_keys(\"admin\")\ndriver.find_element(\"id\", \"password\").send_keys(\"1234\")\ndriver.find_element(\"name\", \"submit\").click()\n<\/pre>\n\n\n\n<p>Here, the <code>\"id\"<\/code> and <code>\"name\"<\/code> values were obtained by inspecting elements on the login page.<\/p>\n\n\n\n<p>Without inspecting elements, the script would fail Selenium wouldn\u2019t know which web component to interact with.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Tools for Inspecting Elements in Different Browsers<\/strong><\/h2>\n\n\n\n<p>Each browser provides a built-in Developer Tool to help users inspect, debug, and modify web elements.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Browser<\/strong><\/th><th><strong>Developer Tool Shortcut<\/strong><\/th><th><strong>Inspector Shortcut<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Google Chrome<\/td><td>F12 or Ctrl + Shift + I<\/td><td>Ctrl + Shift + C<\/td><\/tr><tr><td>Mozilla Firefox<\/td><td>F12 or Ctrl + Shift + I<\/td><td>Ctrl + Shift + C<\/td><\/tr><tr><td>Internet Explorer<\/td><td>F12<\/td><td>N\/A (Inspector under DOM Explorer tab)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Inspecting Elements in Google Chrome<\/strong><\/h2>\n\n\n\n<p>Google Chrome is the most widely used browser for Selenium testing. It\u2019s fast, intuitive, and provides a powerful set of developer tools.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step-by-Step Process<\/strong><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Open Chrome Developer Tools<\/strong>\n<ul class=\"wp-block-list\">\n<li>Right-click on the webpage and select <strong>Inspect<\/strong>, or<\/li>\n\n\n\n<li>Use the shortcut <code>Ctrl + Shift + I<\/code>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Activate the Element Inspector<\/strong>\n<ul class=\"wp-block-list\">\n<li>Click the <strong>arrow icon<\/strong> (top-left of DevTools) or press <code>Ctrl + Shift + C<\/code>.<\/li>\n\n\n\n<li>Hover over the webpage to highlight elements.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Locate the Element<\/strong>\n<ul class=\"wp-block-list\">\n<li>Click on the desired element (e.g., a button or textbox).<\/li>\n\n\n\n<li>Chrome will display its HTML structure on the left and its CSS on the right.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Identify Locators<\/strong>\n<ul class=\"wp-block-list\">\n<li>Find attributes like <code>id<\/code>, <code>name<\/code>, or <code>class<\/code>.<\/li>\n\n\n\n<li>Right-click the HTML line \u2192 Copy \u2192 <strong>Copy selector<\/strong> or <strong>Copy XPath<\/strong>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Test Locators in Console<\/strong>\n<ul class=\"wp-block-list\">\n<li>Use the Chrome console (<code>Ctrl + Shift + J<\/code>) to test locators: <code>$x(\"\/\/input[@id='username']\") \/\/ For XPath document.querySelector('#username') \/\/ For CSS<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Real-World Tip<\/strong><\/h3>\n\n\n\n<p>Many QA professionals prefer Chrome because its DevTools support <strong>live editing<\/strong> of HTML\/CSS. You can modify attributes or text to test dynamic elements before coding Selenium locators.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Inspecting Elements in Mozilla Firefox<\/strong><\/h2>\n\n\n\n<p>Firefox\u2019s <strong>Developer Tools<\/strong> are equally powerful and highly customizable. In Selenium, it\u2019s often used by developers who prefer open-source flexibility.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step-by-Step Process<\/strong><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Open the Developer Tools<\/strong>\n<ul class=\"wp-block-list\">\n<li>Right-click \u2192 <strong>Inspect Element<\/strong>, or<\/li>\n\n\n\n<li>Press <code>Ctrl + Shift + I<\/code>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Highlight the Target Element<\/strong>\n<ul class=\"wp-block-list\">\n<li>Click the <strong>Select Element<\/strong> icon (<code>Ctrl + Shift + C<\/code>).<\/li>\n\n\n\n<li>Hover and click on the web element you need.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Examine the HTML<\/strong>\n<ul class=\"wp-block-list\">\n<li>The selected element\u2019s HTML appears in the <strong>Inspector tab<\/strong>.<\/li>\n\n\n\n<li>Check for attributes like: <code>&lt;input type=\"text\" id=\"username\" name=\"user\" class=\"input-field\"><\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Copy CSS or XPath<\/strong>\n<ul class=\"wp-block-list\">\n<li>Right-click the HTML tag \u2192 <strong>Copy \u2192 CSS Selector<\/strong> or <strong>Copy \u2192 XPath<\/strong>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Test the Locator<\/strong>\n<ul class=\"wp-block-list\">\n<li>Open Firefox Console (<code>Ctrl + Shift + K<\/code>): <code>$x(\"\/\/input[@id='username']\") document.querySelector('#username')<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Unique Features of Firefox Inspector<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Accessibility panel:<\/strong> Checks if web elements are accessible for users with disabilities.<\/li>\n\n\n\n<li><strong>Box model visualization:<\/strong> Helps understand element padding, margin, and layout issues.<\/li>\n\n\n\n<li><strong>Network monitoring:<\/strong> Analyzes requests and responses, useful for testing page load in Selenium.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Inspecting Elements in Internet Explorer (IE)<\/strong><\/h2>\n\n\n\n<p>Although IE is largely replaced by Microsoft Edge, some organizations still rely on legacy systems that use IE. Selenium WebDriver supports IE testing through the <strong>InternetExplorerDriver<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step-by-Step Process<\/strong><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Open Developer Tools<\/strong>\n<ul class=\"wp-block-list\">\n<li>Press <code>F12<\/code> on your keyboard.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Access the DOM Explorer<\/strong>\n<ul class=\"wp-block-list\">\n<li>Go to the <strong>DOM Explorer tab<\/strong>.<\/li>\n\n\n\n<li>Hover over elements in the webpage, and they\u2019ll be highlighted in the DOM tree.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Locate Attributes<\/strong>\n<ul class=\"wp-block-list\">\n<li>Identify unique element properties like: <code>&lt;button id=\"loginBtn\" class=\"btn-primary\">Login&lt;\/button><\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Copy XPath or CSS Path<\/strong>\n<ul class=\"wp-block-list\">\n<li>IE\u2019s tools are less advanced than Chrome or Firefox, so XPath is often manually written.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Limitations of IE Inspector<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>No direct \u201cCopy XPath\u201d option.<\/li>\n\n\n\n<li>Outdated interface.<\/li>\n\n\n\n<li>Slow rendering for complex web pages.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Pro Tip<\/strong><\/h3>\n\n\n\n<p>For better results, install the <strong>IE Developer Toolbar<\/strong> add-on. It improves inspection and provides features similar to Chrome\u2019s DevTools.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How to Choose the Right Locator<\/strong><\/h2>\n\n\n\n<p>After inspecting elements, choosing the right locator strategy is crucial.<\/p>\n\n\n\n<p>Here\u2019s a guide:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Locator Type<\/strong><\/th><th><strong>Best Used When<\/strong><\/th><th><strong>Example<\/strong><\/th><\/tr><\/thead><tbody><tr><td>ID<\/td><td>Element has a unique ID<\/td><td><code>driver.find_element(\"id\", \"username\")<\/code><\/td><\/tr><tr><td>Name<\/td><td>Element has a unique name<\/td><td><code>driver.find_element(\"name\", \"email\")<\/code><\/td><\/tr><tr><td>Class Name<\/td><td>Common styling or repeated layout<\/td><td><code>driver.find_element(\"class\", \"btn\")<\/code><\/td><\/tr><tr><td>XPath<\/td><td>Complex hierarchy navigation<\/td><td><code>driver.find_element(\"xpath\", \"\/\/div[@id='container']\/button\")<\/code><\/td><\/tr><tr><td>CSS Selector<\/td><td>Short and readable locator<\/td><td><code>driver.find_element(\"css selector\", \"input#username\")<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>Rule of Thumb:<\/strong><br>Always use the most stable and shortest locator. Overly complex <a href=\"https:\/\/en.wikipedia.org\/wiki\/XPath\" data-type=\"link\" data-id=\"https:\/\/en.wikipedia.org\/wiki\/XPath\" rel=\"nofollow noopener\" target=\"_blank\">XPath<\/a> may break if the page layout changes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Common Challenges When Inspecting Elements<\/strong><\/h2>\n\n\n\n<p>Even expert testers face challenges. Here are common ones \u2014 and how to solve them:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Challenge<\/strong><\/th><th><strong>Cause<\/strong><\/th><th><strong>Solution<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Dynamic element IDs<\/td><td>Auto-generated element IDs<\/td><td>Use partial match in XPath: <code>contains(@id, 'login')<\/code><\/td><\/tr><tr><td>Hidden elements<\/td><td>Element not visible on page load<\/td><td>Wait using Selenium <code>WebDriverWait<\/code><\/td><\/tr><tr><td>Nested iframes<\/td><td>Element inside an iframe<\/td><td>Switch to iframe: <code>driver.switch_to.frame(\"frameName\")<\/code><\/td><\/tr><tr><td>Shadow DOM elements<\/td><td>Web components inside shadow roots<\/td><td>Use <code>execute_script<\/code> in Selenium<\/td><\/tr><tr><td>Duplicate attributes<\/td><td>Similar elements on a page<\/td><td>Use hierarchical XPath or unique text value<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Testing Locators in Selenium: A Practical Example<\/strong><\/h2>\n\n\n\n<p>Let\u2019s test the process end-to-end.<\/p>\n\n\n\n<p><strong>Step 1:<\/strong> Inspect an element on Chrome<br>Suppose we inspect this element:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">&lt;input type=\"text\" id=\"email\" placeholder=\"Enter email\"&gt;\n<\/pre>\n\n\n\n<p><strong>Step 2:<\/strong> Write a Selenium script<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">from selenium import webdriver\nfrom selenium.webdriver.common.by import By\n\ndriver = webdriver.Chrome()\ndriver.get(\"https:\/\/example.com\")\n\nemail_field = driver.find_element(By.ID, \"email\")\nemail_field.send_keys(\"test@example.com\")\n<\/pre>\n\n\n\n<p><strong>Step 3:<\/strong> Validate in DevTools Console<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">document.querySelector('#email')\n<\/pre>\n\n\n\n<p>If this command highlights the element, the locator works perfectly.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Best Practices for Inspecting Elements in Selenium Testing<\/strong><\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Use Browser Developer Tools Efficiently<\/strong>\n<ul class=\"wp-block-list\">\n<li>Learn all shortcuts to speed up inspection.<\/li>\n\n\n\n<li>Use the console to verify locators instantly.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Prefer Stable Locators<\/strong>\n<ul class=\"wp-block-list\">\n<li>IDs are most stable; XPath should be the last choice.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Regularly Update Locators<\/strong>\n<ul class=\"wp-block-list\">\n<li>Websites change structure often review locators regularly.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Test on Multiple Browsers<\/strong>\n<ul class=\"wp-block-list\">\n<li>Always cross-verify elements in Chrome and Firefox.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Document Locators<\/strong>\n<ul class=\"wp-block-list\">\n<li>Maintain a locator repository for your Selenium framework.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Leverage Plugins<\/strong>\n<ul class=\"wp-block-list\">\n<li>Tools like <strong>SelectorsHub<\/strong> or <strong>ChroPath<\/strong> simplify XPath and CSS path generation.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Real-World Application: Enterprise-Level Testing<\/strong><\/h2>\n\n\n\n<p>In enterprise QA projects, testers handle complex applications with dynamic content. Here\u2019s how <em>inspecting elements<\/em> helps:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Banking applications:<\/strong> Identifying secure form elements using <code>name<\/code> and <code>type<\/code> attributes.<\/li>\n\n\n\n<li><strong>E-commerce sites:<\/strong> Inspecting dynamic product grids and validating \u201cAdd to Cart\u201d buttons using CSS selectors.<\/li>\n\n\n\n<li><strong>Healthcare portals:<\/strong> Navigating deeply nested iframes using XPath inspection.<\/li>\n<\/ul>\n\n\n\n<p>According to a 2024 survey by <em>Test Automation University<\/em>, over <strong>78% of Selenium testers<\/strong> said that mastering element inspection improved their automation success rate and reduced debugging time by 40%.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Why Learn Element Inspection Through a Selenium Certification Course<\/strong><\/h3>\n\n\n\n<p>While self-learning is possible, structured training offers hands-on experience and practical exposure.<\/p>\n\n\n\n<p>Through an <strong>H2K Infosys Selenium certification course<\/strong>, learners gain:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Real-world projects on cross-browser inspection<\/li>\n\n\n\n<li>Exposure to Chrome, Firefox, and IE inspection tools<\/li>\n\n\n\n<li>Practical Selenium WebDriver training<\/li>\n\n\n\n<li>Mentor-led debugging exercises<\/li>\n<\/ul>\n\n\n\n<p>An <strong>online Selenium course<\/strong> allows learners to practice on live web applications while receiving expert guidance making the transition from theory to practical automation seamless.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>Every great Selenium script begins with one simple action inspecting elements.<br>Whether you\u2019re using Mozilla, Chrome, or IE, understanding how to explore and extract web locators is the foundation of successful automation testing.<\/p>\n\n\n\n<p>If you\u2019re ready to elevate your skills, enroll in the H2K Infosys Selenium certification course or our <a href=\"https:\/\/www.h2kinfosys.com\/courses\/selenium-automation-testing-certification-course\/\" data-type=\"link\" data-id=\"https:\/\/www.h2kinfosys.com\/courses\/selenium-automation-testing-certification-course\/\">Selenium course<\/a> online. Gain hands-on experience in inspecting elements, building reliable scripts, and advancing your QA automation career today.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Why Inspecting Elements Matters in Selenium Testing Imagine you\u2019re automating a login test on a website using Selenium. Your script clicks buttons, enters credentials, and validates results all without human input. But have you ever wondered how Selenium knows which button to click or where to type the password? The answer lies in inspecting elements [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":31199,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[43],"tags":[2,5,3],"class_list":["post-1110","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-selenium-tutorials","tag-selenium-online-quiz","tag-selenium-online-test","tag-selenium-skill-test"],"_links":{"self":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1110","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/comments?post=1110"}],"version-history":[{"count":4,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1110\/revisions"}],"predecessor-version":[{"id":31202,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1110\/revisions\/31202"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/31199"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=1110"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=1110"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=1110"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}