specifications

In my routes file I have: resources :subscription, :only => [:show], :constraints => {:protocol => "https"} I'm trying to add a spec for this route like this: it "recognizes and generates #show" do { :get => "/subscription", :protocol => 'https' }.should route_to(:controller => "subscriptions", :action => "show") end However, the spec still fails. If I remove the :protocol => 'https' , the spec also fails: ActionController::RoutingError: No route matches "/subscription" The (undocumented?) solution is to simply include an entire dummy url, like so: it "recognizes and generates #show" do { :get

This question was migrated from Unix & Linux Stack Exchange because it can be answered on Stack Overflow. Migrated 6 years ago . I am looking for a definitive specification describing the expected arguments and behavior of ioctl 0x1268 (BLKSSZGET). This number is declared in many places (none of which contain a definitive reference source), such as linux/fs.h , but I can find no specification for it. Surely, somebody at some point in the past decided that 0x1268 would get the physical sector size of a device and documented that somewhere. Where does this information come from and where can I

Using prompt() I am generating some html to and need to know the maximum length that I can put in the popup. I can't find anything in the spec about this, wondering if someone can help The ECMAScript Programming Language Specification does not specify any maximum length. The maximum length with will be implementation-specific i.e, based on available memory. Here are some real world numbers in case anyone is interested. Please add more if you have any. Using the following code in the browser console: s = prompt("a", Array(SOME_NUMBER).join("0")); s.length; Chrome 43 - 2000 with ellipses as

During the last few weeks, I had the opportunity to read two documents: The MPEG-4 Part 2 specification (ISO/IEC 14496-2), which people just call "mpeg-4" The MPEG-4 Part 10 specification (ISO/IEC 14496-10), which is also called "h.264" or "AVC" After having read all the cool ideas in "mpeg-4" like identifying facial expression, motion of limbs of people, and sprites, I got really excited. The ideas sound very fun, maybe even fantastic, for an idea from 1999. But then I read the "h.264" standard, and none of those ideas were there. There was a lot of discussion on how to encode pixels, but

I need a few input elements, but their values won't be submitted anywhere - they're just going to be manipulated by some client-side JavaScript. Do I have to place them in a <form> to have legit HTML, or can they just be free-standing? For additional information, in xhtml strict you have to place in one of these elements: "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" No. You only need a form if you're submitting to a server. 来源： https://stackoverflow.com/questions/2862050/in-proper-html-must-an-input-be-in-a-form