US Copyright Office Considering MSIE-only website 491
wikinerd writes "The United States Copyright Office asks whether you would have any problem if you were required to use Microsoft Internet Explorer in order to pre-register a work via their website. The Norwegian government recently said no to proprietary formats, but it seems that the US government sites should be informed about the existence of non-Microsoft Web browsers, such as Firefox, Konqueror, Opera, and Safari. I have written a letter about this issue, which is posted on my blog for everyone to copy and base on it their own response. If they see how many people use alternative browsers, they'll probably reconsider and stay within the W3C standards."
But... (Score:2, Funny)
MS Patents (Score:5, Funny)
Re:But... (Score:3, Interesting)
At the level of state abd county governments I'd say that over 80% have problems if you don't run Microsoft products. Most give you Word documents, and assume you are running I.E., usually with Flash.
At least one state University, when confronted on this issue said (and I quote) "Most computers are PC's, and if someone runs some off brand machine instead, they should just buy a PC like the rest of the world"
This statement has so many misconceptions I didn't even respond
m$ domination (Score:2, Funny)
Dumb. (Score:4, Insightful)
"Support for Netscape 7.2, Firefox 1.0.3, and Mozilla 1.7.7 is planned but will not be available when preregistration goes into effect."
So support for other browsers is already planned. I imagine that if enough people complain about it starting out as only IE, they will just postpone this preregistration plan until they have the other browser support ready. All that does is make people who want to use IE wait longer.
Stupid.
Re:Dumb. (Score:3, Insightful)
First, this "planned" status may take unnecessary long. After all, when they are serving the majority of potential visitors with the IE version, there's much less pressure to go and implement the alternate browsers.
Second, and more importantly, if they support all the browsers at the same time, that'll force them, at least to some extent, to make a standards-friendly implementation that will work on all the browsers.
However, if they do IE first, and all the others later, the original version wil
why half-@$$ed -AND- PROPER LETTER (Score:5, Interesting)
Please- Planned means nothing. It means it might be months out when it makes no sense. I can understand Google Toolbar coming out late for Firefix (it's a whole new program), but this is HTML that should display in all browsers.
And a large part of patents is (supposed to be) fairness to all parties. I shouldn't have to go find a Windows machine with IE to hog for a few hours and transfer all my documents over to paste into their Web form. It's something I should be able to do right away. If I can't do it, nobody should be able to (in this case). Otherwise it gives some people *cough* M$ *cough* an advantage on Patents.
Though I'm not a fan of that guy's letter. He touts lists of acronyms like CSS, XHTML, IE, OSX, etc that the developers would know but the _managers_ won't. A simple:
"Internet Explorer, while being used by the majority of Web users, is not used by all Web users. This is in favour of countless browsers (some of which are listed below) which offer considerable advantages to non-Windows users (Mac, Linux) as well as Windows users who are looking for superior alternates to Microsoft's Web browser. Statistics on the number of users utilizing each browser are available at http://..../ [....] Please do not underestimate the 10% of hundreds of millions of US and foreign Web users who choose to utilize alternate technologies. It is unfair to provide an advantage to Windows/Internet Explorer users over others, when it is entirely unnecessary. All Web browsers support standards, such as those set by w3c (http://www.w3c.org/ [w3c.org] which your developers should build their Web site to conform to rather than utilize proprietary methods exclusive to IE.
Simple, to the point, doesn't tout acronyms and explains most of them when it does. References a statistic, and really emphasizes the number of people affected and how common they are.
-M
Re:Dumb. (Score:2, Insightful)
If they write the website using standards, their list of "supported" browsers could be "all standards-compliant browsers".
Yes, I understand that any website must be tested with whatever the more popular browsers of the day are. But they aren't doing anyone a favor by listing these browsers they happen to test a
Slashdot Considers Dupe Free Website (Score:5, Funny)
Re:Slashdot Considers Dupe Free Website (Score:2)
Interesting (Score:5, Insightful)
I would have thought that if the government was under the impression that Microsoft was a monopoly (true or not), they would have taken steps to help prevent adding to that situation, and support a different browser for their site, or *gasp* don't require *ANY* browser, but rather just design it to be functionally usable by any W3C compliant browser. Add in the 508 compliance for web accessbility, and you can't go wrong.
Government, make up your mind.
Re:Interesting (Score:3, Interesting)
It's even worse. I work at a small law office, undergoing ECF (electronic case filing) training and conversion right now. The federal courts, you know the ones which convicted Microsoft of being a monopoly in the browser market, have issued system specs which require Internet Explorer. The mind reels.
Re:Interesting (Score:2)
This was exactly my point.
Luckily some browsers can spoof IE in their browser type settings, although I don't know how well it works since I've never tried it. I'm lucky enough to be in a position to not use si
you are making a poor assumption (Score:2, Insightful)
The president has far more power these days than was ever intended.
Re:Interesting (Score:5, Funny)
2000 U.S. drops suit
2003 U.S. uses Microsoft software exclusively
2005 U.S. forces citizens to use MS software to access government sites
you are here
2012 U.S. forces everyone to use MS software to access the internet
2018 U.S. implants citizens with microchip running MS software
2020 U.S. uses MS software/implants to read your thoughts
2030 U.S. uses MS software/implants to control your actions
Re:Interesting (Score:4, Insightful)
So don't suggest that, because there's no need. All you need to do is test your pages for standards compliance. There's plenty of software around to do that, much of it free. In my experience, all the HTML standards tests are fast and easy to use. And if IE users have a problem with some page, just suggest that they get a standards-compliant browser. There are several available for MS Windows, either free for us cheapskates, or for sale to those suckers who believe "You get what you pay for". Any can be downloaded and installed from IE in seconds; MS hasn't (yet) included code in IE that blocks access to competitors' sites.
Also, complaining about browsers that behave differently is a red herring. HTML was designed from the start to work differently with different browsers. The folks who invented it were well aware of the differences of screens, and wanted something that could be displayed sensibly on both large and small screens. There's also the question of the visually impaired, so HTML should also work with a speech generator. There's very good reason to not want HTML to behave the same everywhere.
It's arguments like your that make your pages not work sensibly on my Blackberry or my wife's Treo, or for blind people. And you're making the bogus claim that you'd have to test for all of them. Nonsense. All you have to do is use some standards-testing software, and make sure your pages pass their tests. That's cheap and easy, easier than testing against N non-standard browsers.
Re:Interesting (Score:5, Insightful)
You have never actually met a customer or an end user, have you? Excluding 90-odd % of the market just isn't an option.
Re:Interesting (Score:5, Insightful)
If you do a bit of homework (or google it) you'll see a pretty stable set of common code that works with all browsers.
The next step is designing a site only using that code. It really isn't rocket science.
Do you sacrifice some cutting edge features? Of course. But unless your purpose is to wow your audience with cutting edge stuff, there should never be a reason to use those cutting edge features.
One of the sites I'm working with now has over 12,000 pages, and is controlled by 3 style sheets. It is clean, compliant code, that has only THREE browser based changes to the stylesheet (in order to make IE work on a couple newer featurs).
The site has forms, online bill pay, dynamic content, flash, rollovers, and is comprised entirely of divs and css.
Sites that say "IE Only", or "Requires standards compliant browser", or any other variation of saying, in essence,
"Please be inconvienced because of my limitations as a designer"
Need to hire a new web team.
It is quite literally zero extra work to make a complex site work with all browsers if you know what you are doing.
And before someone posts 32 specific code examples showing how its impossible, ask yourself, How could I have done that differently? Why did I need to use that code? I will guarantee that there is another way that will work with both browsers, and if not, that you didn't need to implement that in your site.
Re:Interesting (Score:3, Interesting)
Government offices are no stranger to require standards compatibility on other fronts, I see no reason for browsers to be different.
Okay, so maybe most of the standards the government requires are created privately and adopted after much back patting in order to limit potential competition for contracts by denying competitors compliance certification. But that does not mean standards can't be
Re:Interesting (Score:5, Insightful)
That's not true. You still need to test that it works in your browser.
I mean, I just wrote a webpage that includes XForms, SVG, XHTML 1.1, and SMIL. But it doesn't work right in Firefox, Konqueror, Safari, or Opera! I don't get it... I wrote 100% W3C standard-compliant code, and according to Slashdot, if you just code to the standards, it'll magically work in every browser! I'm so confused!
All joking aside, I think what you meant to say is that all he needs to do is code to the standards that Firefox (or Konqueror, etc.) supports. There's a big difference between "writing to the standard" and "writing to the supported standard". Contrary to popular Slashdot belief, you cannot write 100% "standards compliant" code and expect it to magically work the second you bring it up in Firefox. It should work, most of the time. So you're wrong in saying that all this guy has to do is feed his pages through the W3C validator and be done with it.
This "code to the standards" Slashdot mantra really irks me. You guys do realize that even if you write to the standard, it's inevitable that you won't get pixel-perfect pages in every standards-compliant browser, right? Or you may run up against rendering bugs that make "100% standards compliant" pages look different from browser to browser.
Seriously guys, W3C standards are not a magic bullet. They aid interoperability, but they in no way guarantee anything about how your page will look or operate in any given browser. And the worst part about these standards are how many "should" clauses there are -- i.e., "the browser should do X if Y", which leaves lots of things up for interpretation, and incompatibility.
In summary, code to the standards as best as you can. But realize that standards support varies from browser to browser, and you'll inevitably have to provide workarounds.
Standards (Score:5, Funny)
Haha aHahaHaha HahaHaha
HahaHahaHa
haHahaHahaHahaHah
aHahaHahaHahaHahaHahaHahaHaha
etc.
Re:Standards (Score:2)
At least then, nothing will break. In IE it will look like as if it has been through a meat grinder, but it'll work. I can deal with IE-specific sites that break the layout in other browsers, it's the "Here's a clusterfuck we just can't parse" pages that simply won't work in other browsers that frustrate me.
Re:Standards (Score:4, Interesting)
Sure, if you start playing with Javascript, you can get into a real mess, but I'd have felt that just means you should avoid Javascript.
In particular, if a blind user comes to our website, they should see something useful. We can't simulate this perfectly, but we do test the applications in Lynx, and make sure they're usable.
Really, what's so hard about making websites that work in standards compliant browsers?
Re:Standards (Score:5, Funny)
What are you - Jesus or something?
Stop. Supporting. Browsers. (Score:5, Insightful)
These are not fundamentally architecturally different pieces of equipment. If you can't create a website that works adeqautely with all browsers, then you don't deserve to be employed as a web designer.
Re:Stop. Supporting. Browsers. (Score:3, Insightful)
Yes, browsers change faster than the archived information. I'm tired of playing this "cat and mouse" game with browser updates causing one to reedit html files. The US Copyright Office should consider adopting html standards. If MS doesn't want to play along then they can't go screw themselves. Here's the standard I think they should use:
For reference:
XHTML 1.0 The Extensible HyperText Markup Language (Second Edition) [w3.org]
XHTML [wikipedia.org]
If you can't create a website that works adeqa
You have to (Score:3, Interesting)
The problem is that, thanks to MS, your perfectly designed site won't work properly with the most used browser. Remember - MS does NOT support CSS (or html) correctly to standards. They're not going to even try to pass the acid test.
You can say that's MS's problem but it isn't - if your site doesn't render correctly for 90% of the population, then for all prac
Re:Stop. Supporting. Browsers. (Score:5, Insightful)
Well, you know what? Tough shit. Life's hard all around. Let me tell you some day about the vpn solution I had to implement across a dialup link. Oh yeah, and it had to support a full sql application. Any other professional is expected to show, you know, *professionalism* in their field.
Not web designers tho. They expect to be coddled, and allowed to half ass it.
Re:Stop. Supporting. Browsers. (Score:2)
i hate web *designers*.
[*] my metaphorical book
Re:Stop. Supporting. Browsers. (Score:2)
Where I work I had to fight just to have the right to have Firefox installed (I'm a web app programmer who does some design work). Our main designer does not have Firefox installed because she doesn't want to get yelled at by IT staff.
Don't blame the designers *all* the time, because if part of their job was to
Re:Stop. Supporting. Browsers. (Score:4, Informative)
Re:Stop. Supporting. Browsers. (Score:3, Informative)
Web developers work within finite time and resource to hit specific requirements. When fancy bells and whistles are part of the requirement, and cross-browser support is not, off-brand browsers will suffer. Speaking only for the web developers I've worked with, they are quite capable of making sites cross-browser, and in fact usually advocate this to their employer/customer.
When you are writ
Have an opinion? Express it (Score:5, Interesting)
Yes, it's bad that the copyright office wants to make the website IE-only. But look at their reasons, try to address their reasons without sounding condescending and elitist or like a victim of some huge crime. Better yet, get involved in your local politics and make a real difference in your government.
There are many ways to make political hay. Sending form letters to your representatives is, in my opinion, one of the least productive methods of making your voice heard.
Re:Have an opinion? Express it (Score:2, Insightful)
Without constant feedback from their constituencies legislators are operating in a vacuum, with only their own interests and opinions to guide them. Do you trust a politician to operate honorably in that condition? Making yourself personally heard is important if only to remind politicians that you are listening.
On the other hand,
How long will the situation last? (Score:5, Informative)
It'd be easier to respond to their question if they posted an estimated date for when other browsers will be supported.
Re:How long will the situation last? (Score:2)
Re:How long will the situation last? (Score:2)
because of this, IE 'support' gets added last in my projects.
Stupid rules by stupid people or bribery? (Score:2)
99 out of 100 websites (Score:3, Informative)
Re:99 out of 100 websites (Score:2)
Re:99 out of 100 websites (Score:2)
Re:99 out of 100 websites (Score:3, Informative)
Unbelievably, it's not. Have ever talked to these developers? They do it on purpose, because they think it looks good. Not because it causes problems. They like the scrollbar colours to match the colour scheme they have for the website. The fact that it's hard to spot the scrollbars is irrelevant - same as using microscopic font sizes - they just tell you to "get glasses, grandpa".
Anyway, Konqueror applies those scrollbar styles as well, so it
Re:99 out of 100 websites (Score:2)
Ick. I never like it when people sacrifice usability for looks, especially tacky looks.
The fact that it's hard to spot the scrollbars is irrelevant - same as using microscopic font sizes - they just tell you to "get glasses, grandpa".
I think being condescending like this is a bad idea. In fact, ignoring good graphics design is a bad idea, and they are in the wrong for it. Black-on-black (or otherwise poor contrast) scroll bars, if they are done, is
Re:99 out of 100 websites (Score:2)
Frankly, I have not seen this issue. I really have yet to see a web site designed for Firefox or other alternative program such that it tries to shut out MSIE.
"and if so, why" (Score:5, Interesting)
Second, they're not looking for, nor will they likely accept, arguments along the lines of "single-standards are dangerous". And they claim that Firefox and Safari standards are planned for the future. So you need to give them a good reason, now, not to do this.
What are such good reasons?
Well, for one, preregistration is for copyrighted works that "have a history of pre-release infringement". And, as a publisher in such a field, there's no way in hell you're going to expose that information to known security risks, such as MSIE. It's like starting an antitheft service for cars likely to be stolen, then requiring the owners to leave the cars in an unguarded lot with the keys in the ignition.
Likewise, you can argue that no ultra-secure, enterprise-critical information, such as copyright pre-registration data, resides on any machine capable of running MSIE. Again, it's an issue of security. Denying this service to all but MSIE users effectively removes it from all except those who really need it.
Now all you need is someone willing to fire off a letter in sextuplicate.
Safari (Score:3, Interesting)
Re:"and if so, why" (Score:2)
I don't see why I have to come up with any reason.
They are asking if it's acceptable if there site is MS-IE only.
The answer: No, its not.
Reason (if you need one):
1. Not everyone runs Internet Explorer. Not everyone runs Windows.
2. One can come up with a compatible standard complient website without any more work.
3. It's the internet and should run on any platform that conforms to c
Gartner advises against IE-Only development (Score:5, Informative)
ID Number: G00125170, "Design Web Applications for Standards, Not for Browsers", (2 March 2005) [gartner.com]
One little detail missing... (Score:2, Informative)
"In its request for comments, the office made clear that it plans to support other browsers in the future. In an interview, an attorney with the office said that the sticking point was Siebel software that guaranteed compatibility with only selected browsers--including both IE and Netscape 7.02, a browser with negligible market share--in the current Siebel 7.7 software.
The Copyright Office said it planned to upgr
Re:One little detail missing... (Score:2)
It would also be a pointless waste of tax dollars to come up with an interim solution for other browsers when it's already slated to happen for the next revision anyway."
They may well be breaking international trade rules or indeed, various local competition laws.
Ah, Siebel (Score:4, Informative)
Um, requiring a specific browser or office suite? (Score:2)
By requiring Word doc format, they are requiring that you purchase Microsoft Word, requiring that you use Internet Explorer they are requiring that you use Microsoft Windows.
Wonder what the WTO would have to say.
Poor Copyright Office! (Score:3, Funny)
Accessibility (Score:2)
Requirements for commenting (Score:2)
It appears that email isn't an option; and that hardcopies have to be submitted in sextuplicate(!). Even more confusing to me:
That's from the last paragraph
From TFA... (Score:5, Funny)
Which is French for...
"But Mr Dent, the plans have been available in the local planning office for the last nine months."
"Oh yes, well as soon as I heard I went straight round to see them, yesterday afternoon. You hadn't exactly gone out of your way to call attention to them had you? I mean like actually telling anybody or anything."
"But the plans were on display
"On display? I eventually had to go down to the cellar to find them."
"That's the display department."
"With a torch."
"Ah, well the lights had probably gone."
"So had the stairs."
"But look, you found the notice didn't you?"
"Yes," said Arthur, "yes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying Beware of the Leopard."
Re:From TFA... (Score:3, Funny)
You'd think the fine folks at the US Copyright Office would own a photocopier...oh, wait!
Required plug (Score:2)
Frontend for IE core that can also use the Gecko engine for rendering. I don't know too much about how these things work, but I'm a heavy web browser who's used Firefox extensively and I prefer Maxthon. Much faster UI response, doesn't crash/freeze for [me and group] as much as FF, and comes with all the basic important extensions built in. I hate proselytizing, so this is hard for me -- I just want to make people aware of it. Reject it at your leisure.
You should use
Affecting around 29 million Linux/BSD users. (Score:3, Informative)
A reasonable number [li.org] to shun, a sizeable chunk being American. Regardless, I'm increasingly seeing browser/OS statistics that look more and more like this site's [w3schools.com]. On my own site Firefox useage is twice that of MSIE. Linux useage has grown a great amount in the last year and our audience is largely comprised artists, those perhaps interested in registering a copyrighted work.
Re:Affecting around 29 million Linux/BSD users. (Score:2)
Re:Affecting around 29 million Linux/BSD users. (Score:3, Informative)
Browser stats (Score:2)
Re:Browser stats (Score:2)
meaning? (Score:2)
Would that be MSIE as of some freeze-date? Or does the USCO mean to hitch its wagon to Microsoft's development path, so that, e.g., playwrights and composers must also master the art of frequent software-upgrading?
I herewith patent .. (Score:2)
claim 2. The method of claim 1, where the preferred HTTP access method is using Internet Explorer, version 6, or any later version
claim 3. The method of claim 2, where the submitted document holding the patent application is in the patented Adobe document format.
Microsoft might have threathened USPTO (Score:2)
IE 7 Feature enhancement. (Score:2)
Microsft cares for you too
There are degrees of compatibility... (Score:2)
"This site won't work in Firefox because of browser detection scripts that disable it on purpose"
"This site won't work in Firefox because it uses IE-only JavaScript objects"
"This site won't work in Firefox because it depends on an ActiveX object"
So I wonder which it is... I can accept #1 with some grumbling about shoddy design, since it's really not that hard to lay out a site in a compatible way, but I can deal with it. The others are less excu
You know they mean Windows MSIE (Score:2)
When people go the trouble of specifying "IE only" they almost alwasy mean "Windows IE only".
Siebel CRM to blame (Score:5, Informative)
Opinion:
Of course, why they'd use some substandard MS-only piece of garbage is beyond me, but it's not because they were actively looking to cut out non-MS people...just someone suggested a crappy product and standardized on it.
Nothing new.
What about Section 508? (Score:5, Informative)
Section 508 has all sorts of stuff that goes beyond W3C to include formatting, layout, table naming, etc. to ensure that a web site is easily browsable by non-sighted users' browser tools. (i.e. Lynx-like)
They can't do what they are saying they want to do without breaking the law.
(It's not that hard to make a compliant web site, you just need to work it in the process from the beginning.)
Re:What about Section 508? (Score:3, Interesting)
The point is, though, adding support for other browsers doesn't take support away from IE.
More meat for the bones of the author's response (Score:2, Informative)
At the URL:
http://www.copyright.gov/fedreg/2005/70fr44878.htm l [copyright.gov]
I read a proposed policy with title "Preregistration of Certain Unpublished Copyright Claims" which asks me as a member of the public to inform your office if I would have any problem if I were required to use the Microsoft Internet Explorer browser for preregistering a work.
Below you can read my personal opinion and feedback on this issue.
I have no access to Microsoft Internet Explorer because I chose to prevent
Hmm, the usual 2 minutes hate (Score:4, Insightful)
I'm seeing a lot of comments demanding plain-jane HTML, and denying that it costs anything to support multiple browsers, because you just check for "standards compliance". I used to think this. It's completely wrong today. Many web applications today have rich interfaces approaching desktop apps. Getting them to work cross-browser is damn hard. It is definitely worth doing for a mass-market thing like gmail, but for a niche site used by a handful of attorneys? Hard to justify.
Of course, the rich interface is probably not needed or justified in this governmental site.
The problem is not solvable by standards compliance, at least in the automatable sense. You can have CSS that passes validation, looks fine in IE, and piles things on top of each other in other browsers.
Re:Hmm, the usual 2 minutes hate (Score:3, Insightful)
That's not really relevant.
The objections are pointing out that the Copyright Office, as a Government entity, shouldn't be mandating any sort of restriction of access to Government services.
I just spoke to the Copyright office (Score:5, Interesting)
I then spoke to one of the lawyers.
She tells me that
- this spring, Congress mandated that they set up to do this "preregistration" business online by late October;
- that they're funded mostly by registration fees, unlike the patent office, and so do not have a huge budge;
- they're, ahhh, somewhat behind the curve on technology (quote from nice person: "I won't say neanderthal, but..."), and
- the department that's implementing this (direct quote) "will guarantee that the forms will work with IE, but won't guarantee that it will work with other browsers."
I explained how, though I am very much not a Macaholic, most of the artists I have read of or know personally use Macs, which would preclude them from using this system. I also pointed out that not a single Website that takes your credit card requires IE.
She and I had a nice conversation, and she requested that I send the letter w/ five copies. So, folks, send the letters, ASAP.
mark
PS I told her, at the end, that I'd heard of this on slashdot, and her response indicated that she may have heard of
It should be illegal, it may be unconstitutional. (Score:3, Interesting)
The government can't plead expense for new services at least, bec
Re:Swings and Roundabouts (Score:3)
Excuse me but isn't this not the US Patent Office page?, I think copyright and patents are two different things no?
If it is not, then I guess IBM will be kind of pissed off as they are the company that makes most more patents than everyone each year IIRC.
Quite right (Score:2)
Re:Quite right (Score:3, Funny)
That's it, give me your mouse and glasses, you're suspended.
Re:Swings and Roundabouts (Score:5, Informative)
Write an intelligent and well-informed comment to:
Copyright GC/ I&R
P.O. Box 70400
Southwest Station, Washington, DC 20024-0400
Re:Swings and Roundabouts (Score:3, Informative)
(For some reason, they require that "if sent by mail, an original and five copies of any comment should be addressed to...")
Re:Swings and Roundabouts (Score:3, Informative)
Re:Swings and Roundabouts (Score:2)
it would make a point, if they know there's a point to be made.
Re:Swings and Roundabouts (Score:2, Funny)
You must be new here...
Re:Swings and Roundabouts (Score:5, Insightful)
--
Dear Copyright Office:
I am responding to your August 4 notice on Preregistration of Certain Unpublished Copyright Claims (37 CFR Part 202 [Docket No. RM 2005-9]), in which you ask whether potential preregistrants will unable or unwilling to use Internet Explorer 5.1 or higher with the new electronic form. I am one of an estimated 20% of browser users who does not use Internet Explorer.
I understand that the problem is that you will not be able to upgrade to Siebel 7.8 in time for the October 24 launch, and that Siebel 7.7 offers inadequate guarantees of multiple browser support. I understand that you plan to offer multiple browser support "in the future".
I commend your for developing an electronic form and allowing preregistration. However your announcement of this implementation limitation is worrisome for three reasons.
- You do not identify the source of the limitation. If the electronic form will be compliant with modern web standards (http://www.w3.org/ [w3.org]) but will not have been fully tested with other browsers, that is a minor concern. In this case there is high likelihood that all modern browsers will work with the site. If on the other hand the electronic form will actively block other browsers or will contain IE specific code in violation of web standards, this is a larger concern.
- You do not explicitly address section 508 compliance, which as I understand it is a legal requirement upon the Copyright Office. http://www.section508.gov/ [section508.gov] It is hard to understand how section 508 compliant website would be unusable with essentially any modern browser.
- You do not identify a time frame for removal of this limitation. If you will fix things in a few weeks, fewer users will be affected than if you will take a couple years.
Sample for you slashbotters (Score:5, Funny)
OMGWTF!!! U = N00BS!!!1 F1r3f0x pwns IE.
K BYE..
gg
Your Name.
Re:Swings and Roundabouts (Score:2)
Wake up and smell the coffee - Joe Sixpack isn't remotely technical enough to give a two shits about this kind of thing, and won't be for another 5-10 years.
It's all very well saying "let's just sit back and give them enough rope to hang themselves", but that rather relies on:
1) The public
RFTA (Score:3, Insightful)
This is just 'in the first instance'.
Re:RFTA (Score:5, Insightful)
Without a deadline, it can easily get pushed back and back, until they can say it's working fine with IE only; why bother?
Re:RFTA (Score:3, Insightful)
My guess is that they want to see how thier USERS would react to this change. Having 4,000 Slashdotters chime in with their opinion doesn't actually help them find out what their customers need. But, I think a lot of people who would write letters in support of other browsers would never use the system, and are actually just a bunch of un-necessary noise. But those same people are very happy
Re:RFTA (Score:3, Insightful)
Perhaps, but personally I believe the US Government should create everything in a standards based manner that can be accessed by any application that adheres to the standards. Anything less is favoritisim and gives the developer of a particular application an advantage in the market place. The US Patent office has a broad customer base, it consists of every citizen of the US and any corporation that does business in the US. T
Re:RFTA (Score:3, Interesting)
Should they have used photocopiers, when Xerox was the only company that could make them?
Mainframe computers?
There are all types of proprietary systems that we, and the government uses every day.
Here I am, sitting in front of my government-issued Windows computer right now. Getting ready to go into a video-conference that uses Polycom equipment, which will probably include a Powerpoint presentation.
It is everywhere...but some people have just grabbed onto browser choice
Re:Bah! (Score:2, Informative)
Re:firefox (Score:2)
1. That link isn't even what the blurb is talking about
2. RTFA, they're talking about IE + Netscape, not IE only
3. You ate troll bait.
Re:firefox (Score:2, Informative)
Re:firefox (Score:4, Informative)
From the article:
At this point in the process of developing the Copyright Office's system for online preregistration, it is not entirely clear whether the system will be compatible with web browsers other than Microsoft Internet Explorer versions 5.1 and higher. Filers of preregistration applications will be able to employ these Internet Explorer browsers successfully. Support for Netscape 7.2, Firefox 1.0.3, and Mozilla 1.7.7 is planned but will not be available when preregistration goes into effect. Present users of these browsers may experience problems when filing claims.
Translation:
Yeah, we know that we're supposed to provide uniform access and all that, but those stupid hack developers went and built an IE only site. Now we're staring down a government mandated deadline and there's no way we can fix it fast enough. We're kind of fucked at this point, so we'd better bite the bullet and come clean. Lets see if we can marginalize the issue as we do it, then we kill two birds with one stone and maybe even keep our jobs.
So, um, yeah... this has nothing to do with Netscapes IE renderer. Nice try though.
Re:Look... (Score:2)
How about posting a link to your site so we can see this obviously fashionable, mainstream and representative site for ourselves?
Re:follow the standards (Score:3, Insightful)
I keep reading about sites that are IE-only, yet I rarely run into a site that doesn't render in Mozilla. The only exception I can think of is a gaming site whose patch downloader will only work with IE, and Microsoft's own update site.
Maybe if I were visiting more home-brewed sites instead of commercial/large sites I'd have more problems.
Re:at least your government is asking (Score:3, Informative)