The "Add-ons" page Search bar for the "Available Add-ons" tab doesn't work Topic is solved

Users and developers helping users with generic and technical Pale Moon issues on all operating systems.

Moderator: trava90

Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
Andrew Herbert

Re: The "Add-ons" page Search bar for the "Available Add-ons" tab doesn't work

Post by Andrew Herbert » 2020-07-26, 16:07

The same thing happens if you search for "tab". Maybe it wasn't JustOff's fault? :think:

Error console:
Timestamp: 26/07/2020 13:09:38
Error: XML Parsing Error: not well-formed
Location: https://addons.palemoon.org/?component= ... on=28.11.0
Line Number 368, Column 17:
Source File: https://addons.palemoon.org/?component= ... on=28.11.0
Line: 368, Column: 17
Source Code:
<name>Drag & Drop: Search, Open Links, & Open Images</name>

New Tobin Paradigm

Re: The "Add-ons" page Search bar for the "Available Add-ons" tab doesn't work

Post by New Tobin Paradigm » 2020-07-26, 16:58

RESOLVED FIXED - https://github.com/Pale-Moon-Addons-Team/phoebus/commit/8bcfaa26c57ca6cb90c3e245d28fa26345806c0b

Oh it was JustOff's fault.. Just not alone. Every person who didn't use entities in obvious XML is at fault.. And so am I.. But that was implied.

What I am REALLY disappointed in is the Netscape RDF Parser for allowing this in the first place but then again it only has to follow its own rules because this flavor of RDF was created by them a long time ago. The real issue is that there is discontinuity in that present day Add-ons Manager Search isn't using RDF it is using true strict XML. I would suspect that if Netscape had added search integration back in the day it would have used Nestcape RDF and this obviously wouldn't be a problem.