istopwg / website Goto Github PK
View Code? Open in Web Editor NEWPWG.org web site code
License: Apache License 2.0
PWG.org web site code
License: Apache License 2.0
Ira posted an initial draft of "HCD Security Guidelines" back in February. Unfortunately, the IDS WG page (ids/index.html) has no subsection to list working drafts. Add a sub-section for working drafts, and list "HCD Security Guidelines" (https://ftp.pwg.org/pub/pwg/ids/wd/wd-mcdonald-hcd-security-20190213.pdf)
If I click on this to load the PWG home page (http://www.pwg.org) I now expect it to redirect to its TLS equivalent (https://www.pwg.org). Currently that redirection isn't working, but in the past I thought it was.
The objects in the JSON file contains a "family" field. But typing in the "family" in the filter field yields no results. Extend the Filter field backing code so that text typed into the field will also match objects' family field values.
Links such as the one found on this line need to be updated to point to the v1.1 specification:
Line 80 in 2d4a2a3
The v1.1 spec is:
http://ftp.pwg.org/pub/pwg/candidates/cs-ippeve11-20200515-5100.14.pdf
The IDS WG page has a button / link to the current charter. The link needs to be updated to point to the newly approved charter:
https://ftp.pwg.org/pub/pwg/ids/charter/ch-ids-charter-20190826.pdf
If I go to "https://www.pwg.org" the website works as expected.
If I go to "https://www.pwg.org." with a trailing period (which is legal since the period is the "root" of the DNS), the site responds with a 400 Bad Request error page.
Tried it in Safari 13.0.5 & Firefox 73.0 (macOS 10.15.3) and Firefox 73.0 (Ubuntu 18.04.3) with the same results.
If I do a "curl -I https://www.pwg.org." I get a 200 OK but a GET will cause the 400 Bad Request.
Generally if one visits "http://pwg.org" there will be a redirect to "http://www.pwg.org". Bu in some circumstances, the user may arrive at https://pwg.org/dynamo/login.php, and not get redirected, and when that happens their credentials are not accepted.
The "delete an article" feature on the PWG website seems to not work.
Steps to reproduce:
Expected result:
The article is deleted, with perhaps a "confirmation dialog"
Actual result:
The page shows a message "Bad command 'D'." See attached screen shot.
I fixed the links to 5102.1 and 5102.2 in standards.html but the updated links in the file aren't making it to the browser. PHP problem? Tried it in 2 different browsers (Safari and Firefox) and restarted them and problem persists.
website/ippeveselfcert/index.html
Line 101 in b6d13d7
Need to fix the 1.1 Update 1 links to point to the 1.1 Update 1 files (they all point at their equivalent 1.0 Update 5 files), and republish.
These pages aren't updating since server upgrade in early March:
https://www.pwg.org/usage/
https://www.pwg.org/ftp-usage/
Perhaps the facility that was gathering this information never got updated or re-installed...
When I go to the Standards page (https://www.pwg.org/standards.html) and I mouse over the "View" button, the URL is using the "http:" scheme, which doesn't match the URL scheme of the page itself. Perhaps not that big a deal but not ideal either.
On the IPP Everywhere certified printer list page (https://www.pwg.org/dynamo/eveprinters.php) it would be nice to be able to see and filter on products that support PDF and that support roll feed media or various media sizes.
(I was also checking to see why we had "IPPS" as a column - all the certified printers support it, but it is optional with IPP Everywhere. So I guess we ought to keep that column...or make TLS required for IPP Everywhere™ 😊 )
When you login you should be placed on a dashboard page that lists your comments, issues, etc. unless the login was driven by a specific action (e.g. to post an issue, etc.)
It isn't currently possible to show only IPP Everywhere 1.0 or IPP Everywhere 1.1 products. Add a filter option at the top to enable that.
The Create Document page needs some love:
In the "IPP Everywhere Self-Certified Printers" page (https://www.pwg.org/dynamo/eveprinters.php) a listing might need to have its model string fixed. Currently site administrators can edit the listings. If lots of requests for these fixes start coming in, they could cause a lot of housekeeping for site administrators.
As such, if it isn't too hard to implement, add the ability to allow the submitter (or perhaps a new role associated with a particular member's organization) to update the listings.
I logged into the PWG website to try to file an erratum against 5199.10. But I found that the "Informational Documents" section under "Our Work" doesn't provide a "Report Issue" button. I then tried to go to "Review Issues" and "Create Issue", but the Informational Documents aren't listed as a possible choice.
Update the website to support reporting issues with PWG Informational Documents.
There are a few usability issues with the IPP Everywhere and self cert pages:
If for instance you go to this page:
https://www.pwg.org/standards.html
and you look at the date for a document, the system uses the publication date of the document (I'm guessing the date code from the file name) to present the date on the web page. The form to create a listing doesn't have a field to manually set the date.
What is wrong is that the page presents for each document the date for 1 day before the document publication date. For example, IPP 3D Printing Extensions is cs-ipp3d10-20170210-5100.21.pdf, so was published on 2017-02-10, but the site lists its date as "Feb. 9, 2017".
Smith Kennedy reported the following on the IPP WG list:
" I was going to fix the document just now, but when I click on the link for http://www.pwg.org/issues/31 the website refuses to take me to the issue. Same problem if I try to search for issue #31 (http://www.pwg.org/dynamo/issues.php/31?L+P-1+S-2+E0+I30+Z0+Q) - if I click on the 31 it takes me to the PWG homepage.
The link in Process 3.0 to the reflectors points here:
http://www.pwg.org/mailhelp.html
But the menus on the website point to the Mailman main page. Update the menus to point to the mailhelp.html instead (where I added a link to the Mailman main page).
Getting a Javascript warning on the current PWG site concerning the use of a "deprecated" search API. Need to update...
If I fill out an issue form, for instance when updating an issue, if I haven't entered all required information I see "Please correct the highlighted fields". However, no fields are highlighted.
System: OS X 10.11.4, Safari Version 9.1 (11601.5.17.1)
The file "standards.html" has a static version, but the current one on the website is dynamically generated by the "dynamo" CMS. For any page that has a dynamic version and an old static equivalent, the static one should be removed from the repo to avoid confusion about how the site works.
On the "Manage Users" page (https://www.pwg.org/dynamo/accounts.php), typing in a string in the "Search Users" text box at the top, and then clicking "Search", I would expect the number of accounts to be filtered to contain only those listings that contained that substring. But the result list is not filtered. I tried my name ("Smith"), "HP", and "CSR", and none of them had any effect.
It has been published as 5199.10 and is already listed on the Published Standards tab / section - remove from Working Drafts tab / section.
If for instance I type in "5100.1" I expect to see the 3 5100.1 documents, 5100.10-5100.19. So 12 documents. Or if I type in "5100.5" I expect to see 1 document. But it doesn't filter the list at all - it always shows all of the documents.
Didn't we have this problem with articles or something?
Right now you can't have a WG confirm a reported issue without assigning an editor for updating the document, which isn't how we actually want to manage things.
The state should be settable to "confirmed" without an assignee.
When I try to load the pwg.org login page in Firefox (on either Ubuntu 16.04 or OS X 10.11.5) the page is blocked and the user sees a page like the "Firefox connection is not secure page loading blocked for TLS for www.pwg.org" picture.
If I dig into this, it seems that we are using a certificate authority that doesn't seem to have a CA cert that is distributed with Firefox. Here is the list of the CAs in Firefox 47.0:
And here is the Page Info dialog from Firefox, which doesn't provide a "View Certificate" button like Seamonkey does:
And here is the Certificate Info page from SeaMonkey, which has it but I don't quite know why / how I got it:
I'm not sure what to do here other than to either choose a different CA or get Firefox to support our CA so that we don't look dodgy.
It might be more convenient for readers if the "View" button below articles and standards listings open the article in a separate window...but if this is a personal preference thing, and most don't like this preference, we can abandon this change.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.