SEC EDGAR database XML results display, etc.
XML search results from the SEC EDGAR database appear to display now as flat text files under Firefox 153 instead of the SEC's beautifully formatted XML page display.
As a flat text files these are very hard to read.
Also when saving these files for processing, the save name is now "browse-edgar.html" when before it was "SEC.gov _ EDGAR Search Results.html"
Note also that when saving an html file the extention is intermittently .htm instead of .html.
When saving "DOM source of selection.html" as "text files" the extension will change to .txt instead of .html as it was earlier. When I save them a second time the extension will be corrected to .html as it was before. I have to catch these now or my Matlab code won't recognize the files in my download folder. I'm not sure which extension is correct.
(Intel Mac running Tahoe)
Anyway lots of little things with this release.
Thanks for the best browser in the world in spite of them.
การตอบกลับทั้งหมด (4)
This sounds like it's following whatever it receives from the server, incl. content disposition headers and the like, so might have been just a site change of encoding or metadata?
Do you have any particular links that could be checked for the behavior change between versions?
I seem to get it rendered just fine:
I was using this form of the url for looking up a security by name:
https://www.sec.gov/cgi-bin/browse-edgar?company=scienture+holdings&owner=exclude&output=xml
cgi-bin may no longer be working. Including it doesn't throw an error. Excluding it throws a permission error.
This may be a site change. I was able to replicate the issue stepping back to the previous version of Firefox. I never took a screen shot of how it presented before this issue started; so, I can't show the way it's supposed to look.
As far as the save name extension problem, I've noticed that every time I change the format in the save-as dialog, the extension gets truncated to 3 letters in version 153.0.
I ran the link through mozregression to see builds from year ago and it appears the same so that's something the site operator needs to address.
It's a site bug. The URL sends:
content-type: text/html; charset=utf-8
which it is not. And rendered as HTML, it a) has no structure, b) does not have the ability to use the linked XML style transformation.
So they broke something on their side.
Thanks for looking at this jbr.
I've sent a note to their structured data group. We'll see if they can fix it.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.