We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

Disable auto closing of (HTML etc.) tags?

  • 2 amsoshi
  • 1 yana da wannan matsala
  • 20 views
  • Amsa ta ƙarshe daga DTWD

DTWD
DTWD
more options

Is there a way to prevent Firefox trying to be helpful and close tags that aren't closed in code?

We are trying to trace a problem with code built from from about 10 different templates and finding where a missing tag is difficult when the browser keeps closing them. - The page is only "built" just before being delivered to the browser.

I appreciate I am in a minority, but I would rather my development browser fail to render the page instead helping by inserting unclosed tags, in this case in the wrong place hence why we noticed the problem.

Many thanks.

Is there a way to prevent Firefox trying to be helpful and close tags that aren't closed in code? We are trying to trace a problem with code built from from about 10 different templates and finding where a missing tag is difficult when the browser keeps closing them. - The page is only "built" just before being delivered to the browser. I appreciate I am in a minority, but I would rather my development browser fail to render the page instead helping by inserting unclosed tags, in this case in the wrong place hence why we noticed the problem. Many thanks.

Mafitar da aka zaɓa

Are you using the Inspector? In order to build a DOM for you to view, Firefox does sometimes have to guess/decide the boundaries of different elements. So you're right: this view is not useful for your purposes, except that seeing the boundaries in the wrong places may provide important clues.

To see the raw source sent by the server, you can always use Ctrl+u or right-click > View Page Source (not View Selection Source, clear the selection in that case). It's usually ugly, but you could try using a validator to analyze it if pasting it into a syntax-highlighting editor doesn't help you resolve the issue.

Now... if you retrieve HTML in the background and insert it into the page, that is not in the original source. If you use the Network Monitor, you should be able to view the actual server responses to individual AJAX requests. See: https://developer.mozilla.org/docs/Tools/Network_Monitor

Karanta wannan amsa a matsayinta 👍 0

All Replies (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Zaɓi Mafita

Are you using the Inspector? In order to build a DOM for you to view, Firefox does sometimes have to guess/decide the boundaries of different elements. So you're right: this view is not useful for your purposes, except that seeing the boundaries in the wrong places may provide important clues.

To see the raw source sent by the server, you can always use Ctrl+u or right-click > View Page Source (not View Selection Source, clear the selection in that case). It's usually ugly, but you could try using a validator to analyze it if pasting it into a syntax-highlighting editor doesn't help you resolve the issue.

Now... if you retrieve HTML in the background and insert it into the page, that is not in the original source. If you use the Network Monitor, you should be able to view the actual server responses to individual AJAX requests. See: https://developer.mozilla.org/docs/Tools/Network_Monitor

DTWD
DTWD Mai mallakar tambaya
more options

Thank you Jscher, being able to view the source like that is just what we need.

It would have been nice if the inspector had an option for it, but I can drop the code into an editor and work through it.

Thank you!