diff --git a/ui (gen4)/experiments/ig-image-graph.js b/ui (gen4)/experiments/ig-image-graph.js
index 40c63c05..b235a012 100644
--- a/ui (gen4)/experiments/ig-image-graph.js	
+++ b/ui (gen4)/experiments/ig-image-graph.js	
@@ -266,18 +266,6 @@ igImageGraph_template = `
 		text-decoration: underline;
 		opacity: 0.9;
 	}
-	:host .controls button.R:hover,
-	:host .controls button.current.R {
-		background: red;
-	}
-	:host .controls button.G:hover,
-	:host .controls button.current.G {
-		background: green;
-	}
-	:host .controls button.B:hover,
-	:host .controls button.current.B {
-		background: blue;
-	}
 	:host .controls button:hover {
 		opacity: 1;
 	}
diff --git a/ui (gen4)/features/ui-widgets.js b/ui (gen4)/features/ui-widgets.js
index be5faf5b..c0aeba60 100755
--- a/ui (gen4)/features/ui-widgets.js	
+++ b/ui (gen4)/features/ui-widgets.js	
@@ -960,6 +960,25 @@ module.Dialogs = core.ImageGridFeatures.Feature({
 //---------------------------------------------------------------------
 // Universal editor...
 
+
+// XXX EXPERIMENT...
+// 		- how do we handle the ImageGrid context here (i.e. actions)???
+// 			...one way would be to split the fields into two levels, the 
+// 			generic and the domain-specific...
+// XXX REVISE...
+browse.items.Field = 
+function(actions, options){
+	return this([
+		options.title, 
+		options.value instanceof Function ?
+			options.value(actions)
+			: options.value
+	], options) }
+
+
+
+// - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
+
 var EditorActions = actions.Actions({
 
 	// format: