This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26857 - longdesc on iframe should be listed as obsolete
Summary: longdesc on iframe should be listed as obsolete
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 editorial
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard: whatwg-resolved
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-19 12:13 UTC by Simon Pieters
Modified: 2016-04-25 19:53 UTC (History)
6 users (show)

See Also:

Attachments
a crowder.com websight extention to perform tasks. please fix any bugs related to this issue so i can use it. (95 bytes, text/plain)
2016-01-24 06:55 UTC, jen1.6.15m 		Details

Description Simon Pieters 2014-09-19 12:13:14 UTC 

    


    


      



        
          Comment 1
        

        
          jen1.6.15m

        

        
        

        
          2016-01-24 06:23:37 UTC
        

      






this bug was sent by an attachment from crowdflower.com. a websight to do tasks in. please take the blocker off so i can use this extention!

    


    


      



        
          Comment 2
        

        
          jen1.6.15m

        

        
        

        
          2016-01-24 06:55:08 UTC
        

      






Created attachment 1635 [details]
a crowder.com websight extention to perform tasks. please fix any bugs related to this issue so i can use it.

There might be previous bugs related to this issue, please unblock my extention so i can do tasks from crowdflower with it.

    


    


      



        
          Comment 3
        

        
          Arron Eicholz

        

        
        

        
          2016-04-25 19:53:18 UTC
        

      






HTML5.1 Bugzilla Bug Triage: fixed, longdesc is already listed int he obsolete section.

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!