Skip to content
On this page

Known scope

What MageObsidian does not cover, and why. Each item here is a decision or a measured limit, not something left out of sight.

Luma parity

The parity register was read on 2026-10-09 against Magento Open Source 2.4.9. It lists 529 entries: 318 covered, 67 resolved, 142 out of scope and 2 blocked. A covered entry has a test that observed the behaviour, and every block the core contributes to that screen is accounted for. A partial entry has the test, but one or more of those blocks has no counterpart; none is left, and the groups below are the ones that are not covered.

Until 2026-10-06 the register compared screens only, so a screen MageObsidian re-declared counted as covered even when a block another core module added to it was gone. It now also compares the 832 blocks the core declares on those screens. The 71 partial entries it first found came from that comparison, and they were all counted as covered before; none remains.

Found by the functional audit

The screen and block comparison cannot see a store setting that Magento honours inside a block that exists, or a script behaviour with no counterpart. A functional audit of those cases gave the register an origin of its own: each entry names the core setting, template or script that defines the behaviour and the value that triggers it, and it can only be resolved by a test that sets that value. It added 36 entries, and the inventory of the reCAPTCHA forms and the session work added 7 more: 39 resolved and 4 out of scope.

Resolved: the minimum order amount, a reduced quantity, a price change and a line out of stock are announced in the cart and make Proceed to checkout inert; a cart holding a minimum advertised price item says the total comes later; the cross-sell cards add to the bag, the wish list and the comparison like a listing card; an add follows the redirect to the cart when the store asks for it; the side bag honours its display switch, its line limit with an "N of M" link and the edit link; the cart paginates its lines; the "All" page-size limiter no longer breaks the category page; the postal code is optional in the countries the store declares, and the telephone follows its setting; the prefix, middle name, suffix, birth date, gender, tax id, company, fax and VAT number follow their settings in the account forms and the checkout, as does the number of street lines; the configured password length and character classes are announced, enforced and measured; cheque, bank transfer and cash on delivery show the merchant's instructions; a purchase order asks for its number and records it; the bag lines, the totals and the checkout summary state prices, subtotal and shipping with tax, without it or both as the store configures, with the full tax summary and a zero tax hidden when asked; the shipping rates, the estimator's totals and a configurable's price keep both amounts after a variant is chosen; and Fixed Product Tax is included in the price, named by label or stated as one row as configured; a signed-in customer can bill a saved address; the comparison states prices as the listing does, so a minimum advertised price stays hidden, sends a configurable to its page instead of failing to add it, can be emptied in one step and saves to the wish list; a guest is asked to sign in when the store does not allow guest reviews, the reviews of a product are paged, and the cards in category and search listings show their rating; layered navigation drops the product count when the store turns it off, send to a friend offers the configured number of recipients and the advanced search caps its fields at the configured length; and no link points at the newsletter, wish list, reviews or contact page once the store turns the feature off; and the image captcha that waits for failed attempts now appears in the background sign-in once the third one fails; the sign-in sends the reCAPTCHA token, so it works with the challenge on; the browser's cookie settings (domain, path, Secure, website) are published and applied to every cookie the storefront writes; a browser that refuses cookies is told so instead of a mutation failing; Remember Me and the checkout context travel with the background sign-in and registration, so the persistent bag survives them; a recognised visitor is greeted by name with Not you?; and the menu on a phone offers Sign In, Create an Account, My Account and Sign Out; and the product page announces whether the product is in stock and how many are left under the store's threshold, and a downloadable sold link by link prices the links the buyer chooses, with a select-all control; and the compare, wish list and recently ordered sidebars sit under the filters of a category and a search, the new products, recently viewed, recently compared and orders and returns widgets render with the theme's own cards and form, with the recently viewed and compared lists following the store's scope, lifetime and synchronisation settings, and a widget placed in the main content aside or bottom container appears; and each wish list line states the options that were saved and its review summary, keeps an editable quantity and note that survive saving, and has an Edit link that reopens its options, including a configurable's variant; and every document page of an order shows the comments the merchant made visible, offers Print Order and Reorder (Reorder only when the store allows it), the printed invoice, shipment and credit memo state the order status, the order page offers to track its shipments once they carry a number, a refunded downloadable lists its links, the order, invoice and credit memo emails list a bundle's selections and a downloadable's links and itemise Fixed Product Tax, the confirmation page prints the receipt, leads to the downloadable products and offers a guest with a new email an account that takes the order, and the multi-address steps state each line's options and list what needs no shipping; and Google Ads loads its tag on every page and reports the purchase with the order value and currency, through the gtag and through the legacy conversion tag, behind the same cookie consent as Google Analytics 4, and the active RSS feeds are announced in the head, the footer, the category page, the wish list and every order page and document; and the scripts of the checkout, the order confirmation and the multi-address billing step carry Subresource Integrity hashes that match the deployed files, a shopper can move between the store groups of a website, the unsubscribe link of a stock alert email works with and without a script, the logo, the welcome message and the copyright configured in the admin appear, and the fixed texts of the header and the footer follow the store view's language; and, with the optional pickup package installed and the In-Store Pickup carrier active, the checkout offers shipping or pickup in a store, finds the locations that can serve the cart by postal code or city and places the order against the one the shopper chose; and a Page Builder row set to full-bleed reaches both edges of the page without making it scroll sideways, the page chrome clipping its sides without turning the sticky bar's ancestors into scroll containers.

The forms the reCAPTCHA modules protect were inventoried against 2.4.9. The coupon in the cart, the wish list share, the review, send to a friend, registration, password reset, account information, contact, the newsletter and placing an order each render the challenge and accept the answer, with the multi-address review now showing the terms and conditions as well. Two settings have no storefront form to protect and are out of scope: PayPal Payflow Pro, which the checkout does not offer, and resending the confirmation, which core guards only on its REST and GraphQL operation.

Blocked

Two entries are blocked. Neither is a missing feature nobody has looked at; each is a decision the owner took on 2026-10-09 to keep it blocked.

Entry Why it is blocked
Page Builder video background from YouTube or Vimeo A self-hosted video background plays. A provider-hosted one needs the provider's player in a frame, which is a third-party request during page load and a privacy decision. Provider URLs are refused rather than loaded silently. A background plays by itself, so a facade that waits for a click does not apply to it. It unblocks only with a new decision that accepts a third-party player loading during page load.
Server-rendered initial state of the map and banner content types They save an island marker with no initial state inside it, so what they show appears when the island hydrates. Neither moves the page, but neither is readable with no script. It unblocks with a change of its own that delivers a per-request island renderer.

Out of scope

142 entries are out of scope, each with its reason in the register. By family:

Entries Family Reason
53 Renderer declarations Not a screen: they contribute item renderers to another handle.
24 Consolidated screens Equivalent by another route: MageObsidian consolidates what the core splits per product type.
17 PayPal and Payment Services Decided on 2026-08-27 not to build those screens in this project.
15 Fragments and base handles Not a storefront screen: a fragment, a base handle that every concrete one re-declares, or a Knockout endpoint the stack replaced.
7 Wish list items with options Deliberately not used: the item links to the product page instead.
4 Handles with no route The handle has no route on this platform version.
4 Re-expressed behaviour MAP as a native disclosure with no JavaScript, remember-me handled centrally.
3 Swagger tools Development tools served only outside production mode, with their own legacy JavaScript.
2 Off-site payment flows Reaching them needs a payment method that places the order and sends the shopper off-site.
2 Declined products A separately sold checkout and a copy-and-paste component library: decisions taken, not gaps left open.
2 Declined behaviours The catalog list view, which the theme drops on purpose, and inline translation, a development tool.
2 Settings with no storefront form reCAPTCHA for PayPal Payflow Pro, which the checkout does not offer, and for resending the confirmation, which core guards only through its API.
7 Single replacements Product gallery route, the core checkout page layout, a cart handle the platform does not route, a handle no core controller loads, a Page Builder category description template, the review list endpoint, and the first uncacheable search, which is core behaviour.

Payment gateways

No commercial payment gateway has been verified. The extension point is: a payment method can render its own interface inside the checkout, ask for its own fields and hand the shopper over to a gateway and back, and that mechanism is exercised by a purpose-built probe method. A real gateway needs its own verification.

Adobe Commerce

Adobe Commerce is detected and inventoried by mage-obsidian:frontend:doctor, which reports which Commerce-only storefront families a store has enabled. It is not in the compatibility matrix. The full end-to-end verification suite runs on Adobe Commerce 2.4.9 (659 tests passed on 2026-10-13, every failure with a known cause); Adobe Commerce Cloud, payment gateways and Commerce-only features are unverified. See Adobe Commerce.