From af40c6207ab74d511d80bcd5767fc60a256f0b98 Mon Sep 17 00:00:00 2001
From: Tom Willemse
Date: Fri, 19 Apr 2024 22:03:41 -0700
Subject: fix(debug): Don't serve application/xhtml+xml in debug mode

There are quite a few big differences between running HTML and XHTML that are
more than just validation errors. Running a different parser in debug mode seems
unhelpful, and the goal probably won't be to generate XHTML always anyway
anymore.
---
 src/SemanticScuttle/header.php | 10 +---------
 1 file changed, 1 insertion(+), 9 deletions(-)

(limited to 'src')

diff --git a/src/SemanticScuttle/header.php b/src/SemanticScuttle/header.php
index 562ae43..bbe35bc 100644
--- a/src/SemanticScuttle/header.php
+++ b/src/SemanticScuttle/header.php
@@ -158,15 +158,7 @@ $tplVars['userservice'] = $userservice;
 if (!defined('UNIT_TEST_MODE') || defined('HTTP_UNIT_TEST_MODE')) {
     //API files define that, so we need a way to support both of them
     if (!isset($httpContentType)) {
-        if (DEBUG_MODE) {
-            //using that mime type makes all javascript nice in Chromium
-            // it also serves as test base if the pages really validate
-            $httpContentType = 'application/xhtml+xml';
-        } else {
-            //until we are sure that all pages validate, we
-            // keep the non-strict mode on for normal installations
-            $httpContentType = 'text/html';
-        }
+        $httpContentType = 'text/html';
     }
     if ($httpContentType !== false) {
         header('Content-Type: ' . $httpContentType . '; charset=utf-8');
-- 
cgit v1.2.3-54-g00ecf