Custom Filters
Issues List
NOTE: This list has been superseded by http://www.w3.org/Bugs/Public/buglist.cgi?product=CSS&component=Filter%20Effects&resolution=---
Issue 01
- URL
- http://lists.w3.org/Archives/Public/public-fx/2011OctDec/0002.html
- Summary
- shader mesh parameter syntax.
- Proposal
- Accept Chris' proposal.
- Status
- Integrated in 10/19/2011 updated proposal
Issue 02
- URL
- http://lists.w3.org/Archives/Public/public-fx/2011OctDec/0010.html
- Summary
- make it possible for the shader resource to provide a shader mesh default other than 1x1
- Proposal
- Allow the shader resource to contain an optional mesh default to further restrict the use cases when the author has to modify the mesh size.
Issue 03
- URL
- http://lists.w3.org/Archives/Public/www-style/2011Oct/0203.html
- Summary
- highlight that with custom shaders, in particular vertex shaders, the issue of pointer events is becoming more acute.
- Proposal
- No proposal yet, but there is a desire to find a way to a) handle interactivity properly through vertex shaders and b) handle coordinate transforms properly through vertex shaders.
- Status
- Added note to the proposal draft.
Issue 04
- URL
- http://lists.w3.org/Archives/Public/public-fx/2011OctDec/0034.html
- Summary
- Do we need an additional transform uniform to convert coordinates to 'page' space.
- Proposal
- See mailing list reference.
Issue 05
- URL
- none (private email from Fabrice Robinet)
- Summary
- Do we need a way to control texture interpolation (min/mag filters)?
- Proposal
- None at the moment.
Issue 06
- URL
- http://lists.w3.org/Archives/Public/www-style/2011Oct/0545.html
- Summary
- Should we allow turing on blending
- Proposal
- None at the moment.