Turns out the one filter I looked at was already answering either :propagate or :no-propagate, so on the fly I pronounced that a new standard, tweaked the code to respect either in re propagation and otherwise do the usual test of before/after value change. So is this an API change or bug fix? :) ken